Agent skill
verify
Use before any completion claim, commit, or PR — requires running verification commands and confirming output before making success claims
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/verify-dodi-hq-dodi-skills
SKILL.md
Verify
Core principle: Evidence before claims, always.
If you haven't run the verification command in this message, you cannot claim it passes.
The Gate
Before claiming any status:
- IDENTIFY — what command proves this claim?
- RUN — execute it (fresh, complete)
- READ — full output, check exit code
- CONFIRM — does output support the claim?
- THEN — make the claim with evidence
Common Failures
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Test output: 0 failures | Previous run, "should pass" |
| Build succeeds | Build output: exit 0 | "Linter passed" |
| Bug fixed | Reproduce original symptom: fixed | "Code changed" |
| Agent completed | git diff shows changes |
Agent says "success" |
| Requirements met | Line-by-line checklist | "Tests pass" |
Red Flags — STOP
If you catch yourself thinking any of these, run the verification:
- "Should work now"
- "I'm confident"
- "Linter passed" (linter ≠ compiler)
- "Agent said success"
- "Just this once"
Run the command. Read the output. THEN claim the result.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?