verification-before-completion

name	verification-before-completion
description	Use before claiming work is complete or creating PRs. Run verification commands first; evidence before assertions.
when_to_use	[feedback] Triggered before any completion claim, commit, or PR to verify with evidence.

Verification Before Completion

Overview

Core principle: Evidence before claims, always.

Violating the letter of this rule is violating the spirit of this rule.

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

Loop Detection (Pre-Check)

Before running verification commands, check for doom loops:

bash scripts/loop-detector.sh

Interpret exit codes:

• 0 (OK): Proceed with verification
• 1 (WARNING): Reconsider approach. You may be in a loop. Review recent edits before continuing.
• 2 (HARD STOP): STOP. Do not claim completion. Revert to last known good state or seek external input.

If HARD STOP: Do not proceed with verification. The approach itself needs reconsideration.