Verify

SkillAI & models

Makes your agent test that a change actually works before saying it's done.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Verify skill

About this capability

Verify that a change really works before you claim completion

What this skill tells your AI

The instructions your AI receives, as published by yeachan-heo/oh-my-claudecode in skills/verify/SKILL.md and read by ahel’s review.

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

Signals

GitHub stars
39k
Forks
4k
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
verify-yeachan-heo
Source
github.com/yeachan-heo/oh-my-claudecode