verification-before-completion

A skill in obra/superpowers · 321,873 stars on GitHub

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

Security grade of this SKILL.md: SAFE · how we grade

How to install verification-before-completion

npx skills add obra/superpowers --skill verification-before-completion -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule. If you haven't run the verification command in this message, you cannot claim it passes. 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: passes Code changed, assumed fixed Regression test works Red-green cycle verified Test passes once Agent completed VCS diff shows changes Agent reports "success" Requirements met Line-by-line checklist Tests passing Using "should", "probably", "seems to". Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.). About to commit/push/PR without verification. Trusting agent success reports.

Other skills in obra/superpowers

  • brainstorming You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
  • diagnosing-superpowers Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
  • dispatching-parallel-agents Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  • executing-plans Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, o…
  • finishing-a-development-branch Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
  • receiving-code-review Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
  • requesting-code-review Use when completing tasks, implementing major features, or before merging to verify work meets requirements
  • subagent-driven-development Use when executing implementation plans with independent tasks in the current session
  • systematic-debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  • test-driven-development Use when implementing any feature or bugfix, before writing implementation code
  • using-git-worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
  • using-superpowers Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
  • writing-plans Use when you have a spec or requirements for a multi-step task, before touching code
  • writing-skills Use when creating new skills, editing existing skills, or verifying skills work before deployment