Verify and Stop
JuliusBrussee/caveman
Prove existing work meets acceptance conditions without expanding scope. Use for validation-only tasks, completion checks, focused gate runs, and last-mile…
Has the agent prove that a feature, fix or refactor works, using existing tests first, then narrow commands and manual checks, and report only what was actually verified.
Install Verify Before Completion
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode 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/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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/Yeachan-Heo/oh-my-claudecode/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 Yeachan-Heo/oh-my-claudecode --skill verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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 Yeachan-Heo/oh-my-claudecode --skill verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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/Yeachan-Heo/oh-my-claudecode.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 Yeachan-Heo/oh-my-claudecode --skill verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Yeachan-Heo/oh-my-claudecode verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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 Yeachan-Heo/oh-my-claudecode 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 Yeachan-Heo/oh-my-claudecode --skill verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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 Yeachan-Heo/oh-my-claudecode --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 Yeachan-Heo/oh-my-claudecode verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode.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/Yeachan-Heo/oh-my-claudecode/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
- 40k
- Token cost
- ~277 tokens
- SKILL.md length
- 148 words
- Files
- 1
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- MIT
At a glance
Has the agent prove that a feature, fix or refactor works, using existing tests first, then narrow commands and manual checks, and report only what was actually verified.
- Works in 5 steps: Identify the exact behavior that must be… → Prefer existing tests first. → If coverage is missing, run the… → …
- Before announcing that a bug fix or feature is finished
- SKILL.md covers Goal, Workflow, Verification order and Rules, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill replaces "it should work" with concrete evidence. The agent identifies the exact behavior that has to be proven, relies on existing tests first, runs the narrowest direct verification commands when coverage is missing, and falls back to described manual validation with observable evidence when automation is not enough.
The stated order is existing tests, then typecheck or build, then narrow command checks, then manual or interactive validation. The agent may not call a change complete without evidence, must show any failing check plainly, and must say so openly when no realistic verification path exists instead of bluffing. Evidence is summarized concisely rather than pasted as noisy logs, and the report lists what was verified, which commands or tests ran, what passed, and what failed or stayed unverified.
When your agent uses it
- Before announcing that a bug fix or feature is finished
- After a refactor, to confirm behavior did not change
- When a change has no test coverage and needs a direct check
Example prompts
- “Verify that the pagination fix works before you tell me it is done.”
- “Prove this refactor did not break the export command and list the checks you ran.”
- “There are no tests for the new webhook handler, so check it directly and report what you could not verify.”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify the exact behavior that must be proven.
- Prefer existing tests first.
- If coverage is missing, run the narrowest direct verification commands available.
- If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
- Report only what was actually verified.
What it can do on your machine
Read from SKILL.md and the folder at commit 454bae0. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Before Completion loads about 277 tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 148 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 Yeachan-Heo/oh-my-claudecode at commit 454bae0, republished under its MIT licence (© Yeachan-Heo). 148 words, ~277 tokens.
Download SKILL.mdSave it as
.claude/skills/verify/SKILL.md (or your agent's skills folder).- name
- verify
- description
- Verify that a change really works before you claim completion
Verify
Use this skill when the user wants confidence that a feature, fix, or refactor actually works.
Goal
Turn vague “it should work” claims into concrete evidence.
Workflow
- Identify the exact behavior that must be proven.
- Prefer existing tests first.
- If coverage is missing, run the narrowest direct verification commands available.
- If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
- Report only what was actually verified.
Verification order
- Existing tests
- Typecheck / build
- Narrow direct command checks
- Manual or interactive validation
Rules
- Do not say a change is complete without evidence.
- If a check fails, include the failure clearly.
- If no realistic verification path exists, say that explicitly instead of bluffing.
- Prefer concise evidence summaries over noisy logs.
Output
- What was verified
- Which commands/tests were run
- What passed
- What failed or remains unverified
© Yeachan-Heo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/verify of Yeachan-Heo/oh-my-claudecode.
Open the folder on GitHubat commit 454bae0
Compare with similar skills
Verify Before Completion 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 Before Completion this skillYeachan-Heo/oh-my-claudecode | 40k | — | ~277 | Automated safety check: Pass | MIT | |
| Verify and StopJuliusBrussee/caveman | 111k | 1 repos | ~176 | Automated safety check: Pass | Apache-2.0 | |
| Verification Before CompletionjnMetaCode/superpowers-zh | 8.3k | — | ~443 | Automated safety check: Pass | MIT | |
| Iteration Progress Auditprime-radiant-inc/iterative-development | 181 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| QA Verdict JudgeQ00/ouroboros | 6.2k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Nucleus Result Package Builderprotect-my-hair/nucleus-marketplace | 164 | — | ~414 | Automated safety check: Pass | MIT |
Similar skills
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.
Iteration Progress Audit
prime-radiant-inc/iterative-development
Checks the quality of behavior evidence after each iteration in three tiers, using two auditor subagents in parallel to review the same work and find gaps.
QA Verdict Judge
Q00/ouroboros
Gives a fast single-pass quality verdict on any artifact, with a score from 0 to 1, PASS, REVISE or FAIL, and suggestions for what to change.
Nucleus Result Package Builder
protect-my-hair/nucleus-marketplace
Builds the result.json file for a Nucleus V2 workflow run from its context, gates, blockers and step status, and exits non-zero when the run is blocked.
Procoder Commit Gate
azrtydxb/procoder
Applies Procoder's senior-developer discipline in a repository: run the commit gate, format through the binary and work through specs, plans and todos.
More from Yeachan-Heo/oh-my-claudecode
All 47 skills in this repoAsk Advisor Routing
Yeachan-Heo/oh-my-claudecode
Sends a question or task to another locally installed agent CLI, such as Codex or Gemini, through omc ask and saves the answer as a file.
Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
Self-Improve Evolutionary Loop
Yeachan-Heo/oh-my-claudecode
Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.
Autopilot
Yeachan-Heo/oh-my-claudecode
Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.
OMC Mode Cancellation
Yeachan-Heo/oh-my-claudecode
Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.
Hierarchical AGENTS.md Generator
Yeachan-Heo/oh-my-claudecode
Maps a codebase directory by directory and writes linked AGENTS.md files, each pointing to its parent, to document what each area contains.
Related
Categories
Questions about Verify Before Completion
What does Verify Before Completion do?
Has the agent prove that a feature, fix or refactor works, using existing tests first, then narrow commands and manual checks, and report only what was actually verified. This skill replaces "it should work" with concrete evidence. The agent identifies the exact behavior that has to be proven, relies on existing tests first, runs the narrowest direct verification commands when coverage is missing, and falls back to described manual validation with observable evidence when automation is not enough.
When should I use Verify Before Completion?
Verify Before Completion fits situations like: before announcing that a bug fix or feature is finished; after a refactor, to confirm behavior did not change; when a change has no test coverage and needs a direct check.
How do I install Verify Before Completion in Claude Code?
Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a claude-code`. Or copy the skill folder (skills/verify in Yeachan-Heo/oh-my-claudecode) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.
How do I install Verify Before Completion in Codex?
Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a codex`. Or copy the skill folder (skills/verify in Yeachan-Heo/oh-my-claudecode) into .agents/skills/verify in your project. Codex loads it when a task matches its description.
Can I use Verify Before Completion 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 Yeachan-Heo/oh-my-claudecode --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 Before Completion need to run?
SKILL.md names no scripts, command-line tools or credentials: Verify Before Completion is instructions for the agent only.
Does Verify Before Completion access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verify Before Completion 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 Before Completion use?
Verify Before Completion is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify Before Completion use?
About 277 tokens (SKILL.md is roughly 1.1k 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 Before Completion?
Skills that share tags, products or a category with Verify Before Completion: Verify and Stop (JuliusBrussee/caveman, 111k stars), Verification Before Completion (jnMetaCode/superpowers-zh, 8.3k stars), Iteration Progress Audit (prime-radiant-inc/iterative-development, 181 stars) and QA Verdict Judge (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify Before Completion?
Yeachan-Heo (a GitHub user) maintains it in Yeachan-Heo/oh-my-claudecode, which has 39,720 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 2026.
Source: Yeachan-Heo/oh-my-claudecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.