/verification-before-completion
Verification Before Completion
Evidence before claims. If you didn't run the verification in this message, you can't say it passes.
Used by 1 agent
What it does
The iron law: no completion claims without fresh verification evidence. Before asserting tests pass, a bug is fixed, a build succeeds, or a task is done, run the exact command that proves it, read the full output, check the exit code, then state the claim with the evidence. "Should work," "probably fine," and "just this once" are the rationalizations the skill exists to refuse.
Use it before every commit, every PR, every "done" claim, and every status update in a long-running task. Especially load-bearing when you're tired, when an agent reports "success" without diff evidence, or when partial verification is tempting.
Outputs a claim with attached proof: command run, output quoted, pass count or exit code named. No fresh verification, no claim. Pairs with `test-driven-development` (the tests that make verification possible), `systematic-debugging` (the root-cause step before the fix), and `get-shit-done` (the workflow that enforces it as a gate).
