# Verify

AI DevKit · Enforce evidence-based completion claims, require fresh command output...

- Repository: https://github.com/codeaholicguy/ai-devkit (1656 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add codeaholicguy/ai-devkit --skill verify -g -a claude-code -y`
Codex: `npx skills add codeaholicguy/ai-devkit --skill verify -g -a codex -y`
Cursor: `npx skills add codeaholicguy/ai-devkit --skill verify -g -a cursor -y`
Gemini CLI: `npx skills add codeaholicguy/ai-devkit --skill verify -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.
- A change that alters anything a user or caller sees requires a `dev-smoke` run, whatever the claim is called.

## Gate Function

Every completion claim must pass all steps in order:

0. **Classify**, Does the change alter anything a user or caller sees (CLI output, API response, UI, displayed status or state, file formats)? If yes, `dev-smoke` is required evidence alongside tests.
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 in the Report Format below.

If any step fails, stop. Fix the issue and restart from step 0.

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 succeeds | Build output: exit 0 | Linter passing, partial build |
| Bug is fixed | Symptom reproduced at the level the user saw it (CLI/API/UI) → now gone, plus a regression test | "Changed code, should be fixed"; unit test alone for a user-visible bug |
| Linter clean | Linter output: 0 errors | Single file check |
| Phase complete | Each criterion verified individually | "Tests pass, so done" |
| Feature works | `dev-smoke` run or E2E test | Unit tests alone |

## Report Format

The rest: https://github.com/codeaholicguy/ai-devkit/blob/HEAD/skills/verify/SKILL.md