verify
Verify that a change really works before you claim completion
Best for Quality assuranceWorks with GitHubLow risk
⌘source
- author
@Yeachan-Heo- language
- TypeScript
★30kstars
2.7kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Converts vague claims into concrete evidence
- ·Follows prioritized verification order
- ·Requires evidence before declaring completion
- ·Reports exactly what was verified and what failed
- ·Prefers concise evidence over noisy logs
Use Cases
- →Confirming a bug fix actually resolves the reported issue
- →Validating a new feature works as specified before deployment
- →Ensuring a refactored component maintains existing functionality
- →Verifying a security patch doesn't break critical workflows
Best for
- ✓Quality assurance
- ✓Release validation
- ✓Code reviewers
Not ideal for
- !Creative exploration
- !Initial prototyping
FAQs
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
$install
1-click copynpx skills add Yeachan-Heo/oh-my-claudecode --skill verifySafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.