Menu

Individual skill

maintain-prove-it

Improve a repo's generated verification skill from what its past runs learned. Works on both kinds made by /create-prove-it, the permanent prove-<app> and a temporary prove-<migration>. Reads the receipts in .prove-it/runs/ (failed and blocked steps, retries, the commands that finally worked, steps that failed for reasons unrelated to the change, how each change was sorted into checks) and any bug that slipped past prove, then fixes drifted steps, writes in the working commands, adds the check that would have caught a slipped bug and a section for any new surface. For a temporary skill it checks whether the migration is done and, if so, suggests the end step. Never rewrites an answer key (spec, snapshot, old system) to match the app. Proves every edit live and reports product bugs without touching product code. Use for /maintain-prove-it, "update the verify skill", "the verifier is out of date", "prove missed this bug", "prove keeps failing on unrelated steps", or after a big merge or migration milestone.

skills/maintain-prove-it/SKILL.md

Read pinned source

Source commit 0f7e404357e8f5676b5e4a6fcac3560395be8795

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
62
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Maintain Prove It

A verification skill goes stale the day the app changes: a route moves, a button gets renamed, a new surface ships with nothing in the skill that reaches it. A stale skill is worse than none, because the next agent will trust it. Every prove run leaves a receipt that shows where the skill struggled. This pass reads those receipts and folds what they learned back into the skill.

## Rules for the whole pass

- **Only edit the skill's own folder** (SKILL.md, scripts/). Never change product code here.
- **When the app and the skill disagree, work out which one is wrong.** The skill describing something the app no longer does is either *drift* (the app changed on purpose: fix the skill) or a *product bug* (the app broke: report it, don't rewrite the skill to match the bug). Read the commit that changed it. If you still can't tell, ask.
- **Answer keys are not the skill's steps.** The user's spec, the snapshots in `.prove-it/snapshots/` and the old system a flow is compared with say what right looks like. A drifted step can be fixed, but an answer key that disagrees with the app is reported to the user, never rewritten to match. Only the user changes one.
- **Every edit you make to the skill gets proved live before you finish.** An unproven edit is just more drift.
- **Old verdicts are leads, not evidence.** Earlier receipts, closed tickets and status docs tell you where to look. Only this pass's live runs count.
- **Never loosen a check to make a flaky step pass.** Record the failing run, then decide whether the app has a race or the check is ambiguous.

## 1. Find the skill