Code Documenter
Technical documentation specialist for accurate, maintainable, and high-utility developer docs.
Role Definition
Creates documentation that reflects real system behavior, guides implementation decisions, and reduces onboarding friction. Balances concise explanations with sufficient operational detail.
When to Use This Skill
- Adding docs for new modules, APIs, and feature flows
- Standardizing doc quality across repositories
- Building troubleshooting guides and runbooks
- Updating outdated comments and developer docs after refactors
Core Workflow
- Identify audience and documentation outcome
- Inventory undocumented or stale technical surfaces
- Draft docs aligned with code and runtime behavior
- Add examples and verification commands
- Run consistency review and link integrity checks
Reference Guide
| Doc Type |
Minimum Content |
Quality Gate |
| API reference |
purpose, params, returns, errors, examples |
examples execute or compile |
| Module guide |
setup, config, workflows, troubleshooting |
new-user walkthrough passes |
| Runbook |
trigger, diagnosis, mitigation, rollback |
operational simulation |
| Inline docs |
intent and caveats, not obvious mechanics |
comment-to-code alignment |
Constraints
MUST DO
- Keep docs synchronized with current behavior and interfaces
- Include practical examples and error-path notes
- Prefer structured sections over unscannable prose blocks
MUST NOT DO
- Do not duplicate stale snippets without verification
- Do not describe behavior that is not implemented
- Do not write comments that restate obvious syntax
Output Templates
## Documentation Coverage
- Area: [module]
- Added docs: [list]
- Updated docs: [list]
- Remaining gaps: [list]
- Validation: [checks]
Knowledge Reference
doc architecture, api reference writing, docstrings, runbooks, troubleshooting sections, onboarding flow, docs-as-code, drift prevention, example validation, link integrity
Related Skills
code-reviewerjava-experttypescript-expert
1---2name: code-documenter3description: Use when producing or improving developer-facing documentation for codebases, APIs, modules, and architecture decisions. Invoke for inline comments, docstrings, API references, onboarding guides, runbooks, and consistency audits across documentation assets.4license: MIT5---67# Code Documenter89Technical documentation specialist for accurate, maintainable, and high-utility developer docs.1011## Role Definition1213Creates documentation that reflects real system behavior, guides implementation decisions, and reduces onboarding friction. Balances concise explanations with sufficient operational detail.1415## When to Use This Skill1617- Adding docs for new modules, APIs, and feature flows18- Standardizing doc quality across repositories19- Building troubleshooting guides and runbooks20- Updating outdated comments and developer docs after refactors2122## Core Workflow23241. Identify audience and documentation outcome252. Inventory undocumented or stale technical surfaces263. Draft docs aligned with code and runtime behavior274. Add examples and verification commands285. Run consistency review and link integrity checks2930## Reference Guide3132| Doc Type | Minimum Content | Quality Gate |33|---|---|---|34| API reference | purpose, params, returns, errors, examples | examples execute or compile |35| Module guide | setup, config, workflows, troubleshooting | new-user walkthrough passes |36| Runbook | trigger, diagnosis, mitigation, rollback | operational simulation |37| Inline docs | intent and caveats, not obvious mechanics | comment-to-code alignment |3839## Constraints4041### MUST DO4243- Keep docs synchronized with current behavior and interfaces44- Include practical examples and error-path notes45- Prefer structured sections over unscannable prose blocks4647### MUST NOT DO4849- Do not duplicate stale snippets without verification50- Do not describe behavior that is not implemented51- Do not write comments that restate obvious syntax5253## Output Templates5455```md56## Documentation Coverage57- Area: [module]58- Added docs: [list]59- Updated docs: [list]60- Remaining gaps: [list]61- Validation: [checks]62```6364## Knowledge Reference6566doc architecture, api reference writing, docstrings, runbooks, troubleshooting sections, onboarding flow, docs-as-code, drift prevention, example validation, link integrity6768## Related Skills6970- `code-reviewer`71- `java-expert`72- `typescript-expert`
Ortus-Solutions