Require fresh verification evidence before claiming tests pass, builds succeed, or work is complete. Use when finishing a task, creating a PR, or reporting status. Triggers: "done", "fixed", "passes", "ready to merge", "all tests green".
Scanned 9/6/2026
Install to Claude Code
npx -y skills add charlieviettq/awesome-agent-skill --skill verify-before-done --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Verify Before Done?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/charlieviettq-verify-before-done-awesome-agent-skill)More formats (shields.io, HTML) on the badges page.
---
name: verify-before-done
description: >
Require fresh verification evidence before claiming tests pass, builds succeed,
or work is complete. Use when finishing a task, creating a PR, or reporting status.
Triggers: "done", "fixed", "passes", "ready to merge", "all tests green".
---
# Verify before done
## Iron rule
No completion claims without **fresh verification evidence** in the current turn.
## Gate (before claiming success)
1. **Identify** what command proves the claim (test, lint, build, repro).
2. **Run** the full command (not a partial check from memory).
3. **Read** exit code and full relevant output.
4. **Verify** output matches the claim.
5. **Then** state the claim with evidence.
## Common claims vs proof
| Claim | Requires | Not sufficient |
|-------|----------|----------------|
| Tests pass | Test command, 0 failures | Previous run, "should pass" |
| Linter clean | Linter output, 0 errors | Build passed |
| Bug fixed | Repro test passes | Code changed only |
| Requirements met | Checklist vs plan | Tests pass alone |
## Red flags (stop and verify)
- "Should", "probably", "seems to"
- Satisfaction before running checks
- Trusting subagent or prior message without re-running
- Partial verification only
## Requirements met (not tests alone)
- Map plan/spec acceptance criteria to evidence (test output, screenshot, API response, manual step)
- A green test suite does not prove every requirement if scope included non-testable items
## Regression discipline
For bugfixes: failing test or repro first, fix, verify pass, optionally revert fix and confirm fail again.
## Branch completion (lightweight)
- Before claiming PR-ready: tests/lint/build per project norms, no known blockers, user informed of scope
- Do not discard branches, force-merge, or cleanup worktrees without explicit user approval
*Verification gate inspired by [obra/superpowers](https://github.com/obra/superpowers) (MIT).*
## Output format
```text
Ran: pytest tests/foo.py -q
Result: 12 passed, exit 0
Claim: Tests pass for foo module.
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!