maintain-verification-skill

Audits and corrects a project's verification skill and feature map through source review and live testing.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill maintain-verification-skill-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintain-verification-skill
Source: https://github.com/gmackie/agent-skills/tree/main/skills/maintain-verification-skill
Command: npx skills add https://github.com/gmackie/agent-skills --skill maintain-verification-skill-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature maps and verification skills drift out of sync with the application as the product changes, leaving documentation that describes behavior the app no longer has. This Skill runs a periodic maintenance pass that re-verifies every feature against source code and live behavior, then ships at most one PR of proven corrections. ## Core Features & Use Cases - Parallel Source Review: Launches one read-only subagent per feature file to explain how each feature works from source and flag likely documentation drift with citations. - Live Verification Pass: Drives every feature in a real session (server, UI, or CLI) following the verification skill's own launch model, with health checks, evidence preservation, and cleanup invariants. - Scoped Corrections: Edits only the verification skill's own directory, triaging findings into doc drift, harness gaps, or product regressions, and ships a single PR of proven fixes. - Use Case: After a month of product changes, run the maintenance pass on your project's verify skill to confirm the feature map still matches reality and receive one PR containing only the corrections that were actually proven. ## Quick Start Ask the agent to audit the verify skill for this project and report whether the outcome is clean, changed, or blocked.

Frequently Asked Questions about maintain-verification-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a verification feature map up to date?▼

Run a maintenance pass that reads every feature file from source with parallel subagents, then drives each feature live in the app. Proven documentation or harness corrections ship as a single PR; unproven claims are not changed.

How to audit a verification skill in Cursor?▼

Invoke the maintenance skill against the project-local verify skill, typically under .cursor/skills/verify-*/. It locates the target by looking for launch and drive sections plus a feature map, then runs source and live coverage passes.

Does the maintenance pass modify product code?▼

No, edits are strictly limited to the verification skill's own directory, including its SKILL.md, features files, and harness scripts. Behavior the app no longer performs is treated as doc drift or reported as a product regression, never patched in product code.

What happens when a feature cannot be reached during live testing?▼

The feature is marked verified-unreachable only with a concrete prerequisite such as auth, entitlement, OS, or external state, plus the route attempted. If the feature map omits that prerequisite, the omission itself is recorded as documentation drift.

When should I not run a verification skill maintenance pass?▼

Skip it when no project-local verification skill with a feature map exists; the pass stops and points to create-verification-skill instead. It is also unnecessary immediately after generation, since it targets drift accumulated over product changes.