maintain-verify-skill
Refresh a drifted project verify-<app> skill after feature changes. Use create-verify-skill for the first skill, or agent-browser or tuistory for a one-time drive.
Cynnamoroll · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Cynnamoroll/factory-stack --skill maintain-verify-skill技能说明
name: maintain-verify-skill description: "Refresh a drifted project verify- skill after feature changes. Use create-verify-skill for the first skill, or agent-browser or tuistory for a one-time drive." license: MIT compatibility: droid
Maintain verify skill
Check every feature file against source and drive every feature live.
Edit scope
Edit only the verify skill's directory (SKILL.md, features/, and owned scripts). Report product regressions without editing product code. Fix map descriptions that drifted from intended behavior.
Pass
-
Find the target. The project skill under
.factory/skills/verify-*/with launch and drive sections and a feature map. Several candidates: ask which. None: stop and point at/create-verify-skill. -
Index hygiene. Read
features/README.mdand list its sibling files. Fix missing, extra, duplicate, or dead entries. -
Source wave. Issue one
explorerTask per feature file, all in one message. Each explains how the feature works from source, flags likely drift withfile:linecitations, and returns one live-verification recipe. Explorers never drive the app. -
Reconcile. Every feature file has a returned summary. Merge recipes into as few app states as practical. Spot-check cited drift. Check recent commits (
git log --since=<last sync>) for user-facing surfaces missing from the map, and require a source path before calling one missing. -
Live pass. Required even when source looks clean. You drive, serially, following the skill's own Launch section. Drive every feature at least once and hold three rules throughout:
- Run the doctor before the first drive, on each fresh session, and after any failed or surprising drive. If the doctor cannot see the problem, reset or relaunch.
- Evidence survives every cleanup. Check it at its named path.
- Nothing a drive started outlives it. Clean up failed attempts too.
A doctor failure caused by drift in the skill is drift. Fix it and retry once. A feature you cannot reach is
verified-unreachableonly with the concrete prerequisite and the route you tried. -
Triage. Wrong or missing user-facing description: fix the doc. Working behavior the harness cannot drive: fix the harness and drive it again. App behavior that is broken: record it for the user and keep it out of this change.
Done when
The reply names one outcome:
- clean. Every feature got source and live coverage. Nothing changed.
- changed. One commit of corrections, each re-driven live, with every changed file re-read.
- blocked. Coverage or a fix could not finish. Say exactly what blocked it.
It also lists features covered, unreachable prerequisites, confirmed drift, and product regressions found.