Agent skill · software engineering · cursor
maintain-verification-skill
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".
Why this skill is useful
Adds specific procedures and scripts for maintaining verification skills that are not commonly documented.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
Maintain a verification skill A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by /create-verification-skill (or any project-local verification skill with a feature map). 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; nothing worth shipping. No branch, no PR. changed — one PR ships proven doc, harness, 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/, and any harness scripts it owns). 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 0. Locate the target. Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map (usually .cursor/skills/verify-/). Several candidates → ask which one; none → stop and point at /create-verification-skill instead of inventing a target. 1. Index hygiene. Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory. 2. Source wave. One read-only subagent per feature file, launched concurrently. Each explains "how does this user-facing feature work?" from source, flags likely doc drift with citations, and returns one concise live-verification recipe. Children never drive the app and never edit files. Return shape: feature summary / source entry points / likely drift or none / one recipe. 3. Reconcile. Every feature file has a returned summary. Merge overlapping recipes into as few app states as practical. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/maintain-verification-skill