verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Before you install
- Last update
- Files in folder
- 1
- Scripts
- No script files found
- SKILL.md size
- 3.6 KB (about 912 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- obra/superpowers
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add obra/superpowers@verification-before-completionRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add obra/superpowers@verification-before-completion --agent claude-code -y- Project install writes to
.claude/skills/verification-before-completion- Global install writes to
~/.claude/skills/verification-before-completion
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /verification-before-completion.
What it does
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 If you haven't run the verification command in this message, you cannot claim it passes. The Gate Function 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 Build command: exit 0 Linter passing, logs look good Bug fixed Test original symptom:…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Categories
Related skills
- brainstorming
obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
- systematic-debugging
obra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- writing-plans
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
- using-superpowers
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
265K installs 301K - requesting-code-review
obra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available