verify · yeachan-heo — Claude Code skill: what it does, how to install
Turns "it should work" into evidence you can read: which check ran, what passed, and what stayed unverified.
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a claude-codeWhat verify does
Reach for this skill when someone asks whether a change really works and the answer so far is a shrug. It turns that into evidence: which behaviour had to be proven, which command proved it, and what came back.
Verification runs in a set order. Existing tests come first, then typecheck and build, then the narrowest direct command that hits the behaviour, and manual or interactive checks last. When coverage is missing, the skill hunts for the smallest direct check instead of inventing a test suite on the spot.
The file is a single SKILL.md holding the workflow and the rules. Saying a change is done without evidence breaks the first rule, and a failing check has to appear in the report as it happened. If there is no realistic way to verify something, the skill says so outright rather than bluffing. The report covers four things: what was verified, which commands and tests ran, what passed, what failed or stayed unverified.
What it helps with
- prove a fix closes the bug instead of merely compiling
- pick a check to run when the new code has no tests
- report on a refactor without a vague "works for me"
- summarise a verification run without dumping raw logs
- name the parts that stayed unverified
Example prompts for the agent
- Verify that the status change actually works: run the existing tests and show me the output.
- I finished the refactor of `src/auth/session.ts`. Prove that sign-in and sign-out still work.
- If there's no way to check this, say plainly what stays unverified.
How to install verify
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a claude-code2Manually: put the files in place
~/.claude/skills/verify/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/verify/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a codex2Manually: put the files in place
.agents/skills/verify/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a cursor2Manually: put the files in place
.cursor/skills/verify/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Yeachan-Heo/oh-my-claudecode verify2Manually: put the files in place
.github/skills/verify/SKILL.md1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a gemini-cli2Platform CLI
gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode --path skills/verifyManually: put the files in place
.devin/skills/verify/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set26
The whole set →Other versions of verify
Similar
Questions about verify
How do I install verify in Claude Code?
Run npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -a claude-code. The skill lands in ~/.claude/skills/verify/SKILL.md.
What does the verify skill do?
It makes the agent prove a change works before calling the work complete, and report only what it actually checked.
What order does it verify in?
Existing tests first, then typecheck and build, then narrow direct command checks, and manual or interactive validation last.
Source text
SKILL.md · MIT
--- 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 1. Identify the exact behavior that must be proven. 2. Prefer existing tests first. 3. If coverage is missing, run the narrowest direct verification commands available. 4. If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence. 5. Report only what was actually verified. ## Verification order 1. Existing tests 2. Typecheck / build 3. Narrow direct command checks 4. 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 · Yeachan-Heo/oh-my-claudecode