maintain-verification-skill
Audit and repair a project's verification skills, executable adapters, feature coverage, and receipts against current source and live behavior. Use for /maintain-verification-skill or "audit the verify skill".
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- maintain-verification-skill
- description
- Audit and repair a project's verification skills, executable adapters, feature coverage, and receipts against current source and live behavior. Use for /maintain-verification-skill or "audit the verify skill".
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml249 B
03 SKILL.md 正文
Maintain verification skill
Read and follow the project verification contract.
- Locate every project
.agents/skills/verify-*skill, its feature map, and its executable adapter or adopted project-native controller. - Inventory current routes, commands, menus, shortcuts, deep links, and docs. Compare them with the coverage index. Mark each entry point mapped, excluded with a current reason, or missing. Use read-only workers only for disjoint source areas.
- Run adapter help, structured capability discovery,
doctor, and one live baseline before editing. Check that errors give a next action, structured output parses, dry runs preserve state, and cleanup owns only the current run. - Compare every affected mapped recipe with current behavior. Correct only proven drift in the adapter, instructions, commands, evidence, or coverage. Keep the change to one reviewable unit.
- Rerun the changed adapter commands and feature paths. Inspect their receipts, confirm cleanup, and validate every affected skill package.
Completion means no discovered entry point is unaccounted for, every correction has source and live evidence, the adapter contract passes, and unsupported speculative edits are absent.
04 同仓库更多 Skills
why
Why code is this way: design rationale, regressions, and history from evidence. For runtime: how.
unslop
Edit prose to remove AI writing patterns when polishing text or asked to make it sound natural.
typescript-best-practices
Use when writing or reviewing .ts/.tsx code: types, validation boundaries, and API signatures.
sync-pstack
Analyze upstream cursor/plugins pstack changes and guide semantic ports into Codex-native Jstack without overwriting local skills. Use when the user says "sync pstack", "check pstack updates", or asks to update Jstack from upstream.
swarm
Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
statechart
Check a finite TLA+ model and explain its paths and rule failures as a statechart.