verification-before-completionlisted

Evidence before completion claims: identify the command that would prove the claim, run it fresh in this session, read the full output including exit code, and only then state the result — with the evidence. Use when about to report work as done, fixed, passing, or ready; before committing, opening a PR, or moving to the next task; when relaying a subagent's result (verify the diff, not the report); and when adding a regression test (red-green it: revert the fix, watch it fail, restore, watch it pass). Claims match their evidence — 'tests pass' means this session's run with zero failures, not a previous run or an expectation; if verification fails, the deliverable is the actual state with output. Prefer wiring recurring checks into pre-commit or CI over re-remembering them. Not for designing what to verify (a test-strategy concern) — this skill governs the moment of claiming, not the shape of the suite.
grimaldost/craft-collection · ★ 2 · Code & Development · score 68

Install: claude install-skill grimaldost/craft-collection

# Verification Before Completion Evidence before claims — a **rigid** skill. The bright line: **a completion claim is made only after the command that proves it has run in this session and its output has been read.** ## The gate Before stating any status — done, fixed, passing, ready, complete: 1. **Identify** the command that would prove the claim. 2. **Run it**, fresh and in full — not a remembered result or partial check. 3. **Read** the output: exit code, counts, failures, warnings. (`$?` is the LAST command's exit code — read it right after the bare command, never after a pipe; capture output to a file instead.) 4. **State the result that the output supports.** Confirmed → the claim, with the evidence. Refuted → the actual state, with the output. A true "still failing" is a better deliverable than a false "done". ## What claims require | Claim | Requires | Not sufficient | |-------|----------|----------------| | Tests pass | This session's run: zero failures | A previous run, "should pass" | | Linter clean | Linter output: zero errors | A partial check, extrapolation | | Build succeeds | Build command: exit 0 | Linter passing, logs looking fine | | Bug fixed | Symptom re-tested gone **and** a regression test that red-greens | Symptom gone, no test left behind | | Regression test works | Red-green verified (below) | The test passing once | | Delegated work done | The diff inspected, checks re-run | The agent's success report | | Requirements met | Line-b