So I built proof-of-done, a free Claude Code plugin: Claude simply can't finish until the tests, build or lint have passed after its last edit.

Try it inside Claude Code (free, source on GitHub):

/plugin marketplace add WST2002/claude-code-skills
/plugin install proof-of-done@claude-code-skills

https://www.youtube.com/watch?v=ozlYRXQTs-U

A real Claude Code session, shortened: Claude said "fixed" without testing, the plugin made it run the tests, and they found a second bug.

What happened in that session

• I asked: "SAVE10 gives the wrong total, fix it quickly, no need to run the tests."
• Claude edited price.js and said "Fixed."
• proof-of-done blocked the stop: "You changed 1 code file (price.js) but ran no verification after your last edit. Run: npm run test"
• Claude ran the tests. One failed: with the FLAT50 coupon the total became −₹20. Claude had never seen that bug.
• It fixed that too, and all 4 tests passed. Now it was really done.

How it works

1. It watches every edit and every check

• Hooks record each code edit and each test, build or lint run, with its exit code.
• It finds your project's commands on its own: npm, pnpm, yarn, bun, pytest, Go, Cargo, Maven, Gradle, .NET, make.

2. When Claude tries to stop, it asks: is there proof?

• No run after the last edit → blocked, with the exact command to run.
• The last run failed → blocked, with the exit code.

3. It doesn't accept fake proof

• Exit code hidden by | tail, | head or || true → blocked.
• The run passed but 0 tests ran (all skipped, or no test files found, including Go's [no test files] and Jest's --passWithNoTests) → blocked.
• A check that failed, then passed with no edit in between → flagged as flaky.

4. It catches test tampering

• Tests skipped or focused (.skip, .only, @pytest.mark.skip), assertions weakened (toBe(250) → toBeDefined()), tests deleted, errors hidden (@ts-ignore, eslint-disable), coverage thresholds lowered: blocked with the file and line.

5. New code with no test? It asks you once

• If Claude added real code but no test, it asks you whether to add one. Say no, and the report notes why. Small edits, styles and config are left alone.

Get it

• Install: the two commands above, inside Claude Code
• Source (MIT, runs only on your laptop, no network calls): proof-of-done on GitHub
• All my Claude Code skills: github.com/WST2002/claude-code-skills
• More short demos: youtube.com/@wst2002rk
• Featured on the HOL blog: Proof-of-done checks the last change before an agent stops
• Also on Reddit: r/coolgithubprojects

Has your AI ever told you "done" when it wasn't? What did it skip?

Update (28 Oct): Google stopped serving Gemini CLI on personal Google accounts, so which-ai-to-use now hands the task to Antigravity CLI (free) instead. ▶ Watch the new 36-second demo: https://youtube.com/shorts/LCt2H7bFwLg

I use Codex, Claude Code and Gemini CLI on the same projects. The worst moment is when one of them hits its usage limit halfway through a feature. The next AI starts cold: it re-reads half the project, asks what we are building, and still misses the decisions I already made.

After a lot of trial and error, I made which-ai-to-use: a free, open-source tool that hands your task to another AI with the full context, so it carries on instead of starting over.

Try it: install it from VS Code (search which-ai-to-use in Extensions), or run npx which-ai-to-use in any project.

What it does

• Hands your task to another AI. When the limit hits, it writes a handoff note (HANDOFF.md) with the task, your latest requests, where the AI stopped, the commits and changed files, and your test command. Codex, Gemini CLI or any other AI reads it and carries on instead of starting over.
• Reads the chat for you. The task and your requests come straight from your Claude Code, Codex or Gemini CLI chat, so you don't retype anything.
• Keeps your secrets out. API keys, passwords and tokens from the chat are hidden before anything goes into the note.
• Picks who carries on. It suggests the best AI you have installed for the task and starts it with the note. No other AI installed? It tells you which one to get.
• Gives the task back. When Claude's limit resets, it offers to hand the task back to Claude with the same note.
• Tells you which AI to use. For any task, it picks the best of your AI tools and the right model, with a ready command.
• Helps you hit the limit less. It warns you before your 5-hour window runs out, with ways to make it last (like /compact or a smaller model for small edits), and makes your AI skip files that waste tokens: one package-lock.json can be 50,000+ tokens.
• Shows your AI week. Tokens per day next to the week before, and requests per AI.

How to use it

• In VS Code, Cursor or Windsurf: open the Which AI sidebar and click Claude limit over?. It writes the note and shows who should carry on, with a Run in terminal button.
• In a terminal: run npx which-ai-to-use handoff in your project.
• Automatically: the optional Claude Code plugin writes the note the moment the limit is reached. Setup is in the README.

Get it

• VS Code: Which AI to Use on the VS Code Marketplace, or search which-ai-to-use in Extensions
• Cursor, Windsurf, VSCodium: Which AI to Use on Open VSX
• Any terminal, no install: npx which-ai-to-use
• Source: github.com/WST2002/which-ai-to-use
• npm: npmjs.com/package/which-ai-to-use
• Not a developer? The website suggests AI apps for any task
• Short demos: youtube.com/@wst2002rk
• Also on Reddit: r/coolgithubprojects

Everything runs on your laptop and nothing is uploaded. Usage warnings and reports read only numbers from the logs; the handoff reads your latest chat, on your laptop, to write the note. It is tested on real projects (250 tests).

What do you put in your handoff notes? I'd love to know what I'm missing.