Codebase Documenter

**Judgement:** A strong, specialized documentation skill that’s well-suited for systematically documenting small to large codebases, especially where beginner-friendly onboarding and consistency are priorities. **Strengths:** - Comprehensive coverage: README, architecture, API docs, and code comments with clear templates and best practices. - Beginner-oriented: focuses on explaining "why", progressive disclosure, quick-start paths, and concrete examples. - Process-aware: includes a workflow for analyzing the codebase, choosing doc types, generating content, and reviewing for clarity. **Key Risks / Limitations:** - Still dependent on accurate input and correct interpretation of the codebase; it can generate plausible but incorrect documentation if the underlying analysis or provided context is incomplete. - Visual aids (diagrams, flowcharts) are described conceptually; generating and maintaining high-fidelity diagrams may still require manual tooling. - Does not enforce validation of commands or examples; users should manually test generated setup instructions and API examples. **Recommended Scenarios:** - Teams formalizing documentation for an existing project to improve onboarding for new developers. - Solo developers who need structured guidance to produce professional, consistent documentation quickly. - Projects preparing for open-sourcing or handoff, where readability, clarity of architecture, and API discoverability are important. - Organizations looking to standardize documentation patterns (READMEs, architecture docs, API references, code comments) across multiple repos.