verify

name	verify
description	Use before claiming any task is complete, fixed, or passing. Enforces evidence-based completion — no claims without fresh verification. Applies to tests, builds, bug fixes, and requirement fulfillment.
argument-hint	[what you're about to verify]

Verify Before Completion

"Claiming work is complete without verification is dishonesty, not efficiency."

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

Before claiming any status or expressing satisfaction:

1. IDENTIFY — What command proves this claim?
2. RUN — Execute the FULL command (fresh, complete)
3. READ — Full output, check exit code, count failures
4. VERIFY — Does output confirm the claim?
   • If NO: State actual status with evidence
   • If YES: State claim WITH evidence
5. ONLY THEN — Make the claim

Skip any step = lying, not verifying.

Common Failures

Claim	Requires	Not Sufficient
Tests pass	Test command output: 0 failures	Previous run, "should pass"
Build succeeds	Build command: exit 0	Linter passing, logs look good
Bug fixed	Test original symptom: passes	Code changed, assumed fixed
Requirements met	Line-by-line checklist	Tests passing

Red Flags — STOP

• Using "should", "probably", "seems to"
• Expressing satisfaction before verification ("Great!", "Perfect!", "Done!")
• About to commit/push/PR without verification
• Trusting agent success reports without independent check
• Thinking "just this once"

Regression Tests (TDD Red-Green)

Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)

A regression test that never failed is not a regression test.

Anti-Patterns

• "Should work now" — RUN the verification
• "I'm confident" — Confidence ≠ evidence
• Agent said success — Verify independently
• Partial check — Partial proves nothing

Integration

• Use after /tdd to confirm implementation
• Use after /diagnose to confirm fix
• Use before /handoff to ensure clean state
• Apply Goal-Driven principle: success criteria must be verified, not assumed