About verify-claims
verify-claims is a development skill for checking claims against fresh evidence before reporting them. It gives claim-specific verification steps, including a red-green-revert-restore procedure for regression tests.
Key features
- 01Claim-specific verification commands
- 02Subagent result checks using VCS diffs
- 03Red-green-revert-restore test procedure
- 04Requirements checklist against the spec
Use cases
- 01Confirming tests, lint, or builds in the current turn
- 02Checking a subagent's reported changes
- 03Proving a regression test detects the original bug
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/verify-claimsin Claude Code to confirm it loaded.
Details
From the project READMESTARTER_CHARACTER = 🧾
Verify Claims
Three procedures for proving claims with evidence. Each procedure runs before the claim is made, not after.
Verification Commands by Claim Type
Map the claim to the command that proves it. Run the command in this turn. Use the actual output, not memory of prior runs.
| Claim | Command | Insufficient |
|---|---|---|
| Tests pass | Project test command, full suite or named test | Prior run, "should pass" |
| Linter clean | Project linter command | Partial check, extrapolation |
| Build succeeds | Project build command, exit 0 | Linter passing, logs look fine |
| Bug fixed | Test that reproduces the original symptom | Code changed, "looks fixed" |
| Regression test works | Red-green-revert-restore (see below) | Test passes once |
| Subagent completed | VCS diff plus targeted re-check | Subagent self-report |
| Requirements met | Re-read spec, line-by-line checklist | Tests passing |
Subagent Result Verification
Subagents report success in their final message. The report is not evidence. The diff is.
When a subagent returns:
- Read the subagent summary
- Run
git statusandgit diffto see what actually changed - If the subagent claimed tests pass, run the test command in the current turn
- If the subagent claimed a bug is fixed, run the reproduction case in the current turn
- Only then accept the result and move on
Subagents fabricate success reports under pressure. Treat the report as a hypothesis to verify, not a fact to accept.
Red-Green-Revert-Restore for Regression Tests
A test written after the fix passes immediately. Passing immediately proves nothing. To prove the test catches the bug:
- Write the regression test
- Run it with the fix in place. Expect: pass.
- Revert the fix only.
- Run the test. Must fail.
- Restore the fix.
- Run the test. Expect: pass.
If step 4 passes, the test does not exercise the bug. Throw it out and write a new one.
This procedure is unnecessary when test-driven-development order is followed (test first, then fix). It is the recovery procedure for the inverted order.