superpowers-verify
Skill2 starsChanged 6 months agoMITView on GitHub
Evidence-before-claims gate. Run verification commands and confirm output BEFORE making any completion claims. This skill should be used before committing, marking tasks done, or claiming any fix is complete.
In this repository3 other files it gives its agents.
- superpowers-debuggingSkill
- superpowers-planSkill
- superpowers-tddSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If you haven't run the verification command in this message, you cannot claim it passes.
- Distinctive: line 56
Tests: Run the command, see the count, report the count.
- Distinctive: line 57
Build: Run build, see exit 0. Linter is not a compiler.
- Distinctive: line 58
Agent delegation: Check VCS diff, verify changes, report actual state.
- Distinctive: line 62
No shortcuts for verification: Run the command. Read the output.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verification Before Completion
Overview
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf 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 verifyingCommon Failures
| Claim | Requires | Not Sufficient |
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check |
| Build succeeds | Build command: exit 0 | Linter passing |
| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
| Agent completed | VCS diff shows changes | Agent reports "success" |
Red Flags — STOP
Using "should", "probably", "seems to". Expressing satisfaction before verification ("Great!", "Done!"). About to commit without verification. Trusting agent success reports. Relying on partial verification. ANY wording implying success without having run verification.
Key Patterns
Tests: Run the command, see the count, report the count. Never "should pass." Build: Run build, see exit 0. Linter is not a compiler. Agent delegation: Check VCS diff, verify changes, report actual state. Never trust agent reports.
The Bottom Line
No shortcuts for verification. Run the command. Read the output. THEN claim the result. This is non-negotiable.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.