- Home
- Skills
- Workflow Automation
- Proof of Done: stop AI agents faking "done"
Proof of Done: stop AI agents faking "done"
Sets up Proof of Done, an open-source check that sends AI coding agents back when they delete, skip or weaken tests, or claim the tests pass when they don't.
Free
Works with the AI Agents you already use
Proof of Done: stop AI agents faking "done"
Example session with this skill installed
Install Proof of Done in this Vitest project, check "all tests pass" claims, and add the pull request check with @dev-team as the owner.
- Read your context and instructions
- Compiled the proof of done
Proof of Done is set up: the Claude Code hook, the claim check for Vitest, and the pull request check with @dev-team as code owner. Nothing is committed yet.
What I ran
$ npm install --save-dev proof-of-done
$ npx proof-of-done install claude-code
Installed Claude Code hooks (SessionStart, Stop) in .claude/settings.json
Launcher: .claude/hooks/proof-of-done.mjs (checks Proof of Done's own files before every run)
Claude Code will now be asked to fix tampered tests (deleted, skipped, emptied or faked) before it can finish.
$ npx proof-of-done install github --owner @dev-team
Created .github/workflows/proof-of-done.yml
Added /.github/, /.claude/, /.proofofdone.yml to .github/CODEOWNERS
$ npx proof-of-done verify
✓ PASS no tampering detected
Files
| File | What it does |
|---|---|
.claude/settings.json | Registers the SessionStart and Stop hooks |
.claude/hooks/proof-of-done.mjs | Launcher that refuses to run a modified copy of Proof of Done |
.proofofdone.yml | Test command for checking "all tests pass" claims |
.github/workflows/proof-of-done.yml | Pull request check |
.github/CODEOWNERS | Changes to the checker need @dev-team's review |
# .proofofdone.yml
version: 0
tests:
command: npx vitest run --reporter=junit --outputFile={junit}
timeoutSeconds: 300
# .github/workflows/proof-of-done.yml
name: Proof of Done
on:
pull_request:
types: [opened, synchronize, reopened, labeled, unlabeled]
permissions:
contents: read
jobs:
proof-of-done:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: wasaybuilds/proof-of-done@v0
Next steps (yours)
- Review and commit
.claude/,.github/,.proofofdone.yml,package.jsonandpackage-lock.json. - Start a new Claude Code session so the hooks apply.
- In GitHub → Settings → Branches, for your main branch:
- require the
proof-of-donestatus check - require review from Code Owners, dismiss stale approvals, require approval of the most recent push
- don't allow bypassing these settings
- require the
- Code owners need write access, and the reviewer must not be the account your agent pushes from.
- After upgrading proof-of-done, run
npx proof-of-done install claude-codeagain.
Connects securely to your tools. The creator never sees your data.
About this skill
AI coding agents sometimes "finish" by deleting the failing test, adding .skip, weakening an assertion until it passes, or saying "all tests pass" without running them. This skill sets up Proof of Done, an open-source (MIT) checker by the author of this skill. It compares your tests before and after a change. It never reads the agent's report, and no LLM is involved.
What it catches
- Deleted or skipped tests: whole files, single tests,
.skip/xit/@pytest.mark.skip, a newly added.only - Removed or weakened assertions:
toBe(120)→toBeDefined(),assertEqual→assertTrue, commented-out asserts - Assertions that can't fail:
expect(true).toBe(true),assert True, asserts swallowed bytry/catch - Edits to the guardrail itself: CI workflows, its config, its hooks
- False "all tests pass" claims (optional): re-runs your tests and reads the JUnit XML report, never the console
It doesn't punish refactors: renamed and moved tests are recognised, and changes the user explicitly asked for aren't blocked.
What the skill sets up
- Claude Code hook: when the agent tries to finish, it's sent back with exactly what to restore.
- Claim check (optional): a
.proofofdone.ymlwith your runner's JUnit command (Vitest, pytest, Jest, Mocha, Go via gotestsum). - Pull request check: a GitHub Action, plus CODEOWNERS entries so changes to the checker need a human review.
- Verification: runs
npx proof-of-done verifyto confirm the setup.
Why not just tell the agent not to cheat?
Instructions are part of what the agent can ignore. Proof of Done runs outside the agent: in a hook, and as a required check on pull requests.
Known limitations
- Test parsing covers JavaScript, TypeScript and Python. The claim check works with any runner that writes JUnit XML.
- The hook is for Claude Code. With other agents, the skill sets up the GitHub Action and the CLI.
- An agent with every permission bypassed can disable local hooks. The required pull request check is the part it can't reach.
- Hardcoded expected values aren't detected yet.
- The skill installs the check; it doesn't replace it.
Network use: the skill runs npm install / npx, which download the package from npm. Proof of Done itself makes no network calls.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Requires Node.js 20+. Git repository must have at least one commit. "All tests pass" verification requires JUnit XML support from the test runner.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 2 days ago
- Free with an Agensi account
- Software
Node.js
Gitproof-of-donevitestjestmocha
- Optional
GitHub
Windows: run the commands in PowerShell or Git Bash. Commit the files the skill creates so your team gets the same checks.
Permissions
Allowed Hosts
File Scopes
Shell runs npm/npx and git. Network access downloads proof-of-done from npm. Files written: Claude Code hook settings and launcher, the Proof of Done config, the pull request workflow and CODEOWNERS entries