Claims
ruvnet/ruflo
Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.
AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success.
Apache-2.0Auto-check passed
Install Verify
$ npx skills add codeaholicguy/ai-devkit --skill verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codeaholicguy/ai-devkit verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify .claude/skills/verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add codeaholicguy/ai-devkit --skill verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codeaholicguy/ai-devkit verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verify .agents/skills/verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codeaholicguy/ai-devkit --skill verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codeaholicguy/ai-devkit verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verify .cursor/skills/verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/codeaholicguy/ai-devkit.git --path skills/verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add codeaholicguy/ai-devkit --skill verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codeaholicguy/ai-devkit verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verify .gemini/skills/verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install codeaholicguy/ai-devkit verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add codeaholicguy/ai-devkit --skill verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verify .github/skills/verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codeaholicguy/ai-devkit --skill verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codeaholicguy/ai-devkit verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verify .opencode/skills/verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/codeaholicguy/ai-devkit/tree/main/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify- GitHub stars
- 1.6k
- Token cost
- ~823 tokens
- SKILL.md length
- 450 words
- Files
- 2
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success.
- Works in 5 steps: Identify — What command proves this… → Run — Execute the full command now. No… → Read — Read complete output. Check exit… → …
- Completing any task
- SKILL.md covers Hard Rules, Gate Function, Verification Patterns and Regression Verification, plus 3 more sections
- Calls npx
What it does
Verify is an agent skill from codeaholicguy/ai-devkit. 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.
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.
When your agent uses it
- Completing any task
- Finishing a phase
- Making any it works claim
Example prompts
- “it works”
- “/verify”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify — What command proves this claim? If multiple commands are needed, run the gate once per command.
- Run — Execute the full command now. No partial runs, no skipping.
- Read — Read complete output. Check exit code. Count pass/fail.
- Confirm — Does the output prove the exact claim?
- Report — State the result, cite command, exit code, and key output.
What it can do on your machine
Read from SKILL.md and the folder at commit 90dcca0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verify loads about 823 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 450 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from codeaholicguy/ai-devkit at commit 90dcca0, republished under its Apache-2.0 licence (© codeaholicguy). 450 words, ~823 tokens.
Download SKILL.mdSave it as
.claude/skills/verify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- verify
- 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.
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:
- Identify — What command proves this claim? If multiple commands are needed, run the gate once per command.
- Run — Execute the full command now. No partial runs, no skipping.
- Read — Read complete output. Check exit code. Count pass/fail.
- Confirm — Does the output prove the exact claim?
- 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 succeeds | Build output: exit 0 | Linter passing, partial build |
| Bug is fixed | Reproduce symptom → now passes | "Changed code, should be fixed" |
| Linter clean | Linter output: 0 errors | Single file check |
| Phase complete | Each criterion verified individually | "Tests pass, so done" |
| Feature works | E2E test or manual walkthrough | Unit tests alone |
Regression Verification
For bug fixes, a single pass is not enough:
- Write a test covering the bug.
- Run → must pass (fix in place).
- Revert the fix.
- Run → must fail (proves test catches the bug).
- Restore the fix.
- Run → must pass.
If step 4 passes, the test is wrong. Rewrite it.
Show full SKILL.md (164 more words)Show less
Red Flags and Rationalizations
| Rationalization | Why It's Wrong | Do Instead |
|---|---|---|
| "This change is trivial" | Trivial changes break things constantly | Run the check |
| "I ran it earlier" | Code changed since then | Run it again now |
| "The test is flaky" | Flaky ≠ ignorable | Fix the flake first |
| "It compiles, so it works" | Compilation ≠ correctness | Run the tests |
| "The CI will catch it" | CI is a safety net, not a substitute | Verify locally first |
| "The agent said it's done" | Agent claims need verification too | Check diff and run tests |
Memory Integration
After a failed verification, store the failure pattern: npx ai-devkit@latest memory store --title "<failure pattern>" --content "<what failed and how to avoid>" --tags "verify,failure-pattern"
Task Tracing
If a task name is known and tracing is usable, record task evidence after
the verification report per task. If tracing was not probed, run the real read
probe first. If probe or evidence recording fails, report the failed task command
and continue verification; never block verification on optional task logging.
© codeaholicguy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/verify of codeaholicguy/ai-devkit.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 90dcca0
Compare with similar skills
Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verify this skillcodeaholicguy/ai-devkit | 1.6k | — | ~823 | Automated safety check: Pass | Apache-2.0 | |
| Claimsruvnet/ruflo | 74k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Verification Before Completionfarm-fe/farm | 5.6k | 46 repos | ~1k | Automated safety check: Pass | MIT | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Full Output Enforcementsickn33/agentic-awesome-skills | 47k | 1 repos | ~889 | Automated safety check: Pass | MIT |
Similar skills
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
Requirements
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
Full Output Enforcement
sickn33/agentic-awesome-skills
A skill your agent uses when a task requires exhaustive unabridged output, complete files, or strict prevention of placeholders and skipped code.
Verification Before Completion
jnMetaCode/superpowers-zh
Chinese-language rule that bars an agent from claiming work is done, fixed or passing until it has run a verification command and read the output.
More from codeaholicguy/ai-devkit
All 28 skills in this repoAgent Management
codeaholicguy/ai-devkit
AI DevKit · Manage running AI agents with ai-devkit agent commands.
Dev Lifecycle
codeaholicguy/ai-devkit
AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.
Task
codeaholicguy/ai-devkit
AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.
Simplify Implementation
codeaholicguy/ai-devkit
AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.
Agent Communication
codeaholicguy/ai-devkit
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.
Technical Writer
codeaholicguy/ai-devkit
AI DevKit · Review and improve documentation for novice users.
Questions about Verify
What does Verify do?
AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Verify is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success.
When should I use Verify?
Verify fits situations like: completing any task; finishing a phase; making any it works claim.
How do I install Verify in Claude Code?
Run `npx skills add codeaholicguy/ai-devkit --skill verify -a claude-code`. Or copy the skill folder (skills/verify in codeaholicguy/ai-devkit) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.
How do I install Verify in Codex?
Run `npx skills add codeaholicguy/ai-devkit --skill verify -a codex`. Or copy the skill folder (skills/verify in codeaholicguy/ai-devkit) into .agents/skills/verify in your project. Codex loads it when a task matches its description.
Can I use Verify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codeaholicguy/ai-devkit --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.
What does Verify need to run?
Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Verify access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verify use?
Verify is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify use?
About 823 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify?
Skills that share tags, products or a category with Verify: Claims (ruvnet/ruflo, 74k stars), Verification Before Completion (farm-fe/farm, 5.6k stars), Requirements (rizsotto/Bear, 6.5k stars) and Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify?
codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,643 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.
Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.