Verification before completion
Skill vrennat/developersDevelopers/skills/verification-before-completion
Use when about to claim work is complete, fixed, passing, or ready. Requires running the verification command and showing its output before any success claim.From its SKILL.md
npx -y skills add vrennat/developersDevelopers --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Verification Before Completion
Fires when Claude is about to claim "done", "fixed", "passing", "ready", or any equivalent. Before any such claim, evidence must be produced. A claim is either about a gate ("tests pass") or about behavior ("the handler now rejects expired tokens", "this is equivalent to the old path"). Gates need a green command; behavior needs ground truth.
Procedure
- Identify the relevant verification command (typecheck, test, build, lint — whichever matches the claim).
- Run it. Capture the output.
- Pass: include the output verbatim in the response, then make the claim.
- Fail: do NOT claim done. Surface the failure. Continue work.
- For a claim about what the code does (not just a green gate): re-read the actual source you are asserting about before claiming. Do not trust your earlier summary or memory of it. Equivalence claims ("same as before", "matches the spec") are testable — prove them: diff the two, run both, compare output.
Example
Bad: "Tests are passing now."
Good:
$ bun run test:run
✓ src/lib/foo.test.ts (12)
Test Files 1 passed (1)
Tests 12 passed (12)
Tests pass.
Behavior claim — bad: "The webhook now verifies signatures." Good: re-open the handler, confirm verifySignature(raw) runs before JSON.parse, quote the lines, then claim.