| name | maintain-verification-skill |
| description | A repo's verification skill, feature map, or .claude/verify.sh gate has drifted from the app. Audits every feature from source and live, ships proven fixes. Use for 'audit the verify skill'. |
Maintain a verification skill
A feature map rots the moment the app changes, and a verify.sh gate rots more quietly: it keeps exiting 0 while checking less and less. This skill is the upkeep loop for a project's verification setup — the skill generated by create-verification-skill, or any project-local verification skill with a feature map, plus the .claude/verify.sh Stop-hook gate that sits alongside it.
The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.
Outcomes
Pick one, and say which:
- clean — every feature got source and live coverage, the gate was audited; nothing worth shipping. No branch, no PR.
- changed — one PR ships proven doc, harness, gate, or map corrections.
- blocked — coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.
Edit scope
Only edit the verification skill's own directory (its SKILL.md, features/, any harness scripts it owns) and .claude/verify.sh. Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).
Pass
-
Locate the targets. Find the verification skill: the project-local skill whose body has launch/drive sections and a feature map (usually .claude/skills/verify-*/). Several candidates → ask which one; none → stop and point at instead of inventing a target. Also locate ; its absence is itself a finding, since the Stop hook is a silent no-op without it.
