Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →archive228/verification-before-completion
Use before claiming work is complete, fixed, or passing — before committing, opening a PR, or handing off. Requires running the verification command in THIS turn and reading its output before any success claim.
Passed 17 of 20 test cases with the skill, and 15 of 20 without it.
and 1 more in the full report
4 fixed15 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I generated a SQL migration file using `prisma migrate dev --create-only`. Can I report that database schema migration is complete?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that generating a migration file is distinct from executing and verifying the migration against a database | Passed | Passed |
| The response requires running the migration and verifying applied schema state before declaring completion | Missed | Passed |
The instructions your model reads when the skill loads.
Claiming work done without fresh verification is dishonesty, not efficiency. adversarial-verify is the what; this skill is the when — the gate you pass through right before any completion claim.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you have not run the verification command in this message, you cannot claim it passes. Not "should", not "probably", not "based on the diff".
Before writing "done" / "fixed" / "green" / "ready to merge" — even in your own head:
Skip any step = you are lying to the user, not verifying.
| Claim | Requires | Not sufficient |
|---|---|---|
| Tests pass | Fresh test run, exit 0, 0 failures | "should pass", previous run, "logic looks right" |
| Linter clean | Linter output, 0 errors | Partial check, extrapolating from unrelated files |
| Build succeeds | Build command, exit 0 | Linter passing, editor squiggles gone |
| Bug fixed | Reproduce original symptom, watch it not happen | Code changed, "assumed" fixed |
| Regression test works | Red → green cycle verified (revert fix, watch test fail, restore, watch pass) | Test passes once |
| Agent/subagent completed | Read the VCS diff, verify claimed changes exist | Agent's own "success" report |
| Spec satisfied | Line-by-line checklist against the plan | "Tests pass, phase complete" |
test cases passed, vs 15 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.