1.5 KiB
1.5 KiB
name, description, permalink
| name | description | permalink |
|---|---|---|
| verification-before-completion | Require fresh verification evidence before any completion or success claim | opencode-config/skills/verification-before-completion/skill |
When to Load
Load this skill immediately before claiming work is complete, fixed, or passing.
Core Rule
NO COMPLETION OR SUCCESS CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you did not run the relevant verification command for this change, do not claim success.
Verification Gate
Before any completion statement:
- Identify the exact command that proves the claim.
- Run the full command now (no cached or earlier output).
- Check exit code and output details (failure count, errors, warnings as relevant).
- Report the result with concrete evidence.
- If verification fails, report failure status and next fix step.
- If verification passes, state success and include proof.
Common Proof Examples
- Tests pass → fresh test run shows expected suite and zero failures.
- Lint is clean → fresh lint run shows zero errors.
- Build succeeds → fresh build run exits 0.
- Bug is fixed → reproduction scenario now passes after the fix.
- Requirements are met → checklist is re-verified against the implemented result.
Anti-patterns
- "Should pass" / "probably fixed" / "looks good"
- claiming completion from partial checks
- relying on old command output
- trusting status reports without independent verification
Bottom Line
Run the right command, inspect the output, then make the claim.