Generate the project's own verify skill: build/test/lint commands discovered by running them, a feature map of what each covers, manual checks, and an earned first verdict. Run once per repo.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The bundled verify skill demands evidence but cannot know this repo's
commands. This skill generates the project-local verify skill that makes
verification concrete — by discovering the commands through execution, not
by guessing from a README.
.claude/skills/verify/ and work will be verified here
more than onceprettier --write,
eslint --fix) mutate tracked files — record the read-only check form
(prettier --check, eslint --check) as the verification command, never
the mutating one.run/visual-verdict) exercises, and
what "looks right" means for each..claude/skills/verify/SKILL.md containing: the exact
commands with expected outcomes, the manual checks, the feature map, and
the escalation path (which failure means what, who owns it). Keep it
short enough that a fresh session reads it whole. If a verify skill
already exists at the canonical root (.omc/skills/verify/SKILL.md or
.claude/skills/verify/SKILL.md), respect it: update its commands and
feature map in place rather than overwriting, and say what changed.appendLedgerEntry and defaultLedgerPath from the installed package's
dist/features/verification-ledger/index.js (babysit's ledger step
demonstrates the exact invocation); never append raw rows to
.omc/state/verification-ledger.tsv — the writer owns header creation,
locking, and cell sanitization. The verdict is the one the flow actually
earned: a real UI exercised is live-ui-verified, a test suite run is
unit-test-verified, only build/lint/typecheck passed is
type-check-only, and nothing runnable is no positive row at all.execute.maintain-verification-skill
re-syncs this artifact.Yeachan-Heo/oh-my-claudecode
dec7e41
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.