verify
AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.
Profile →npx skills add codeaholicguy/ai-devkit --skill verify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Verify Prove it works before saying it works. ## Hard Rules - Do not claim completion without fresh terminal evidence from this session. - Forbidden words in completion claims: "should", "probably", "seems to", "likely", "I believe", "I think it works". These signal unverified assertions. - Cached, remembered, or previous-session output is not evidence. Run it again. ## Gate Function Every completion claim must pass all 5 steps in order: 1. **Identify** — What command proves this claim? If multiple commands are needed, run the gate once per command. 2. **Run** — Execute the full command now. No partial runs, no skipping. 3. **Read** — Read complete output. Check exit code. Count pass/fail. 4. **Confirm** — Does the output prove the exact claim? 5. **Report** — State the result, cite command, exit code, and key output. If any step fails, stop. Fix the issue and restart from step 1. If no verification command exists (e.g., no test suite), tell the user and ask them how to verify before claiming done. ## Verification Patterns | Claim | Required Evidence | Not Sufficient | |---|---|---| | Tests pass | Test output: 0 failures, exit 0 | Previous run, "should pass now" | | Build succeed
- Hard Rules
- Gate Function
- Verification Patterns
- Regression Verification
- Red Flags and Rationalizations
- Memory Integration
- Task Tracing
What does the verify skill do?
AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.
How do I install it?
Run `npx skills add codeaholicguy/ai-devkit --skill verify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From codeaholicguy/ai-devkit, a repository with 1,572 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.