# Maintain Verification Skill

> Audit and repair a project-local verification skill and its feature map using source inspection plus one live pass. Use when verification instructions, harness commands, selectors, or documented user features may have drifted.

- Skill: `canepro/maintain-verification-skill` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add canepro/maintain-verification-skill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/canepro/maintain-verification-skill/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: Canepro (https://skillmd.com/u/canepro)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/canepro/maintain-verification-skill

---


# Maintain a verification skill

Keep a repository's verification skill honest. Cover every mapped feature from
source, exercise every reachable feature through the real user-facing surface,
and ship at most one focused correction to the verification skill itself.

This workflow adapts pstack's `maintain-verification-skill` for a shared Agent
Skills layout. It does not authorize product-code changes.

## Outcomes

Finish with exactly one outcome:

- `clean`: Every mapped feature received source and live coverage. No change is
  needed.
- `changed`: One verified change repairs the skill, its feature map, or a helper
  it owns.
- `blocked`: Coverage could not finish safely. Name the exact missing
  prerequisite or failed proof.

## Locate the owner

Find the repository-owned verification skill, usually under
`.agents/skills/verify-*/` or an established equivalent. If several harness
paths exist, resolve their targets and identify the single canonical owner.
Stop on divergent copies instead of editing all of them independently.

If no verification skill exists, use `create-verification-skill` rather than
inventing a maintenance target.

## Audit and repair

1. Compare the feature-map index with its feature files. Fix missing, duplicate,
   stale, or dead entries.
2. Read the source path for every mapped feature. Record likely documentation,
   selector, command, or prerequisite drift with exact source references.
3. Sweep recent user-facing code changes for important features missing from
   the map. Require a concrete source path before adding one.
4. Follow the verification skill's own launch and doctor contract. Temporary
   listeners must bind to loopback. Do not drive an instance whose identity,
   build, or health is uncertain.
5. Exercise every reachable mapped feature. Capture proof before cleanup and
   confirm the proof survives cleanup. Re-run doctor after surprising behavior.
6. Classify each mismatch:
   - Wrong instructions or feature description: repair the verification skill.
   - Working product that the harness cannot drive: repair the owned harness.
   - Broken product behavior: report the product defect. Do not hide it by
     changing the verification contract.
7. Re-drive every corrected path before shipping. Remove only processes and
   scratch state started by this run.

Keep edits inside the canonical verification-skill directory. For `changed`,
review every changed file and ship one focused commit or pull request when the
repository task includes normal collaboration. For `clean` or `blocked`, do not
create a change merely to record the run.