← ClaudeAtlas

verification-before-completionlisted

Run verification commands and confirm output before claiming success. Use when about to claim work is complete, fixed, or passing, before committing or creating PRs.
secondsky/claude-skills · ★ 248 · AI & Automation · score 90
Install: claude install-skill secondsky/claude-skills
# Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. **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 ``` ## Common Verification Commands **Tests:** ```bash # Preferred: bun bun test # Alternative: npm npm test ``` **Build:** ```bash # Preferred: bun bun run build # Alternative: npm npm run build ``` **Lint:** ```bash # Preferred: bun bun run lint # Alternative: npm npm run lint ``` **Type check:** ```bash # Preferred: bun bunx tsc --noEmit # or: npx tsc --noEmit ``` ## Common Failures | Claim | Requires | Not Sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Linter clean | Linter output: 0 errors | Partial check, extrapolation | | Build succeeds