Verify

This is the antidote to "looks good to me" without actually checking. It enforces a verification workflow before claiming anything is done: run existing tests first, fall back to typechecks or narrow commands, and if you have to verify manually, document what you actually observed. The four-tier hierarchy (tests, build, direct commands, manual validation) keeps you honest about what was proven versus what was assumed. Useful when you're working on unfamiliar codebases or want to avoid the classic "it works on my machine" followed by immediate bug reports. It won't let you or Claude hand-wave completion without concrete evidence.

skills.sh installs: 698
GitHub stars: 40.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yeachan-heo/oh-my-claudecode --skill verify --agent claude-code

Installs into .claude/skills of the current project.

Files

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.