Agent skill
maintain-docs
Process session summaries and skill usage logs, identify documentation issues, and apply frequency-gated fixes. Use periodically to maintain project documentation quality.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/maintain-docs
SKILL.md
Process Feedback and Maintain Documentation
Phase 1: Evaluate session summaries
- Read all
.mdfiles infeedback/summaries/that haven't been processed yet- Check
feedback/issue-tracker.mdto see which summaries are already listed as sources
- Check
- For each new summary, identify doc/skill issues: incorrect information, missing guidance, confusing instructions, stale examples
- If deeper investigation is needed, read the raw transcript in
feedback/transcripts/(if still on disk) - Record findings in
feedback/issue-tracker.mdwith file path, issue description, and source summary
Phase 2: Review skill usage
- Read
feedback/skill-usage.logif it exists - Identify:
- Skills never invoked (candidates for removal or better descriptions)
- Skills invoked frequently (candidates for optimization)
- Skills with consistent post-invocation errors in summaries (need fixing)
- Record findings in
feedback/issue-tracker.md
Phase 3: Apply fixes (frequency-gated)
- Read
feedback/issue-tracker.md - Only act on issues reported by 2+ independent sessions (or 1 session with concrete evidence like a build failure)
- For each actionable issue:
- Read the referenced doc/skill file
- Only edit sections within
<!-- AUTO-MANAGED: feedback-driven -->markers (or add new auto-managed sections) - Make minimal, targeted fixes
- If an issue requires substantial work, create a document in
docs/describing the problem and proposed fix instead
Phase 4: Prune and consolidate
- Scan docs/skills for redundant or conflicting instructions — flag for human review
- Print summary of all changes made and issues deferred
Constraints
- Do NOT edit content outside
<!-- AUTO-MANAGED: feedback-driven -->markers - Do NOT act on single-occurrence reports — require 2+ independent sessions (or 1 with concrete build/test failure evidence)
- Do NOT delete documentation or skills — only flag candidates for human review
- Do NOT rewrite entire files — make minimal, targeted fixes
- Do NOT maintain
.claude/HISTORY.md— that is the history-keeper agent's responsibility
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?