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
Install
npx skills add obra/superpowers@verification-before-completionRuns in your terminal. Adds the skill globally for Claude Code, Cursor, Codex and others; add -g -y to skip prompts.
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.
View source on GitHubBefore you install
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.
Categories
Related skills
- brainstorming
obra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
349K installs 281KDesign & UI - systematic-debugging
obra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
246K installs 281KTesting - writing-plans
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
238K installs 281KDesign & UITestingDocumentation - 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
234K installs 281K - requesting-code-review
obra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
218K installs 281KCode reviewGit & GitHub - executing-plans
obra/superpowers
Use when you have a written implementation plan to execute in a separate session with review checkpoints
201K installs 281KAI & agentsCode review