verification-before-completion Skill
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 Published by openai in plugins.
What is verification-before-completion Skill?
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 Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use verification-before-completion Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/superpowers/skills/verification-before-completion/SKILL.md
What it does
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
Skill instructions
Verification Before Completion Overview Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule. The Iron Law NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE If 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 verifying Common Failures | Claim | Requires | Not Sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Linter clean | Linte
Explore related resources
Frequently asked questions
What is verification-before-completion?
verification-before-completion is a open-source AI agent skill with Copy skill directory. 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.
Who is verification-before-completion best for?
verification-before-completion is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install verification-before-completion?
Install or run verification-before-completion using Copy skill directory. Check verification-before-completion for the latest setup command.
Is verification-before-completion actively maintained?
verification-before-completion may need a closer maintenance check before production use.
Auto-fetched from GitHub.
