doc-maintain
Skill2 starsChanged 6 days agoMITView on GitHub
Maintain documentation through stale-doc refresh, architecture codemap generation, or a bounded Markdown refactor. Selects update, codemap, or refactor while preserving each output and evidence contract. Not for application source, tests, manifests, route tables, generated projections, or broad policy review.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- change-verdictSkill
- code-simplifySkill
- code-traceSkill
- create-prSkill
- deploy-listSkill
- feature-verifySkill
- flow-driveSkill
- flow-guideSkill
- git-smart-commitSkill
- git-worktreeSkill
- harness-setupSkill
- issue-analyzeSkill
- js-static-checksSkill
- laravelSkill
- legacy-characterization-testsSkill
- library-authorSkill
- merge-prepSkill
- module-designSkill
- nextjsSkill
- openspec-artifact-guardSkill
- opsx-apply-resumeSkill
- phpSkill
- phpunitSkill
- precommitSkill
- project-auditSkill
- project-briefSkill
- proposal-analyzeSkill
- pr-summarySkill
- pythonSkill
- reactSkill
- release-creatorSkill
- repo-intakeSkill
- repo-verifySkill
- swiftSkill
- tdd-workflowSkill
- ui-ux-verifySkill
- vue-2-notesSkill
- yii1Skill
The file
Files
Documentation maintenance
- Select the mode from the requested output below. A command's fixed mode or explicit mode wins; clarify ambiguous target ownership before editing.
- Resolve the remaining normalized arguments as that mode's consumer input. Record the target, existing dirty work, canonical evidence and any locale pair.
- Load only the selected mode procedure and apply its local completion gates.
- Return its report with the actual PASS, NOT_RUN, BLOCKED or human-decision state. Keep source implementation, installation and release evidence separate.
| Mode | Task and input | Procedure | Output and authority |
| update | Stale documentation path or workflow keyword | update | Documentation update report; PASS/NOT_RUN/BLOCKED/Need Human; documentation only |
| codemap | Structural change or architecture refresh of live consumer tree | codemap | Five CODEMAPS documents and codemap-diff report; PASS/BLOCKED/confirmation-required; preserve the 30% overwrite gate |
| refactor | One existing, safe Markdown path | refactor | Refactored path, before/after line counts, preserved facts; PASS/NOT_RUN/BLOCKED |
Authority is documentation-only: application source, tests, manifests, route tables and generated runtime projections belong to their respective owners. An update does not refresh codemaps or refactor an unrelated file. A refactor retains facts and policy; a codemap refresh keeps its output-path restrictions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.