Verification before completion
Never claim completion without fresh verification evidenceFrom its SKILL.md
npx -y skills add a-ariff/ariff-claude-plugins --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 557 tokens by cl100k_base, as published. Nobody here has run it
Verification Before Completion
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the command in THIS message, you cannot claim it passes.
The Gate
Before claiming ANY success:
1. IDENTIFY → What command proves this claim?
2. RUN → Execute the FULL command
3. READ → Full output, check exit code
4. VERIFY → Does output confirm the claim?
5. CLAIM → Only now, with evidence
Skip ANY step = lying, not verifying.
What Requires Verification
| Claim | Requires | NOT Sufficient |
|---|---|---|
| "Tests pass" | Test output: 0 failures | "Should pass", previous run |
| "Build works" | Build output: exit 0 | Linter passing |
| "Bug fixed" | Test of original symptom | "Code changed" |
| "Linter clean" | Linter output: 0 errors | "Looks right" |
| "Feature complete" | All requirements checked | "Tests pass" |
Red Flags - STOP
If you catch yourself:
- Using "should", "probably", "seems to"
- Saying "Great!", "Perfect!", "Done!" before running verification
- About to commit without fresh test run
- Thinking "just this once"
- Feeling tired and wanting to be done
STOP. Run the verification.
Rationalization Prevention
| You Think | Reality |
|---|---|
| "Should work now" | RUN IT |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ tests |
| "I'm tired" | Exhaustion ≠ excuse |
Correct Patterns
Tests:
✅ [run test] → See "34/34 pass" → "All tests pass"
❌ "Tests should pass now"
Build:
✅ [run build] → See "exit 0" → "Build passes"
❌ "Build looks good"
Requirements:
✅ Re-read requirements → Check each → Report gaps
❌ "Tests pass so it's complete"
Why This Matters
From actual failures:
- User said "I don't believe you" - trust broken
- Undefined functions shipped - would crash at runtime
- Missing requirements - incomplete features
- Time wasted on false completion → redirect → rework
Bottom Line
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.