Doc Maintainer Skill
Create, update, and validate documentation. Keep docs concise, accurate, and scannable.
Activation Triggers
- Documentation not updated after feature implementation (automatic)
- README.md exceeds 150 lines (automatic)
- Go public functions/types missing doc comments (automatic)
- Explicit documentation request (manual)
Documentation Standards
README.md
- 150 lines max. Describe current state only (no timeline/changelog)
- Use CI badges for dynamic metrics (never hardcode)
- Required sections: Overview, Tech stack, Setup, Structure, Features, Dev commands, License
- Prohibited: Detailed tech explanations, unused platform info, verbose descriptions
CLAUDE.md
- Prescriptive tone ("should"). Describe ideal state, not current status
- Dev guidelines in CLAUDE.md, usage instructions in README.md (separation of concerns)
Code Comments
- Go: Required for public functions/types (start with function name). Explain why
- TS: JSDoc for public APIs. Skip when types are self-documenting
- Common: Describe current behavior only. Keep only actionable TODO/FIXME
Workflow
- Analyze: Read existing docs and project CLAUDE.md, identify gaps and inconsistencies
- Verify: Check length limits, temporal info leaks, hardcoded metrics. Run
mcp__ide__getDiagnosticsfor Markdown lint - Optimize: Logical structure, important info first, consistent terminology and style
- QA: Verify alignment with codebase, validate links, test code examples