Verification Before Completion
Independent PiSkill directory guide. The original skill remains hosted by Superpowers.
What is Verification Before Completion?
Requires fresh evidence before an agent claims work is fixed, passing, or complete, making it especially useful for validating AI-generated code before commits or pull requests.
What does Verification Before Completion do?
Verification Before Completion is a Superpowers skill for preventing an AI agent or developer from declaring work finished without fresh evidence. Before saying that tests pass, a build succeeds or a bug is fixed, it requires the exact proving command to be run and its complete result checked.
Who is Verification Before Completion best for?
- Teams validating AI-generated code before merge
- Developers using autonomous coding agents
- Projects where inaccurate 'done' claims create rework
- Code-review and release workflows that require evidence
Common use cases
- Require fresh test output before claiming tests pass
- Verify a build before commit or pull request
- Re-test the original symptom before saying a bug is fixed
- Check requirements and diffs instead of trusting an agent success message
How does Verification Before Completion work?
The skill uses a gate: identify the command that proves a claim, run it fresh, read the full output and exit status, compare the evidence with the claim, and only then state success. Different claims require different evidence; one passing check cannot substitute for another.
Key benefits
- Prevents stale or assumed verification
- Makes completion claims auditable
- Encourages the correct check for each type of claim
- Especially useful before commits, pull requests and handoffs
Things to know
- It verifies the checks you choose; incomplete test coverage can still miss defects
- Fresh evidence does not guarantee that requirements themselves were correct
- Teams still need to decide which verification commands are authoritative for the project
Compatible tools
Frequently asked questions
What checks should run before merging AI-written code?
Why is Verification Before Completion useful for AI code?
Related skills
Finishing a Development Branch
Verifies completed development work and guides the final merge, pull-request, branch-cleanup, or integration decision only after tests have passed.
Test-Driven Development
Enforces test-first implementation for features, bug fixes, refactors, and behavior changes using a strict red-green-refactor workflow and explicit verification.
Systematic Debugging
Guides agents through root-cause-first debugging for test failures, production bugs, performance problems, build failures, and unexpected behavior instead of guessing at fixes.
Receiving Code Review
Helps agents evaluate code-review feedback technically before implementing it, verify suggestions against the codebase, and avoid blindly accepting incorrect or incomplete review comments.
Requesting Code Review
Structures code-review requests around the actual implementation, requirements, and git diff so issues can be caught before they reach the main branch.
Azure Diagnostics
Investigates Azure application and infrastructure failures using resource state, logs, metrics, configuration, and dependency evidence, then recommends scoped remediation.