Audit project documentation and generate consistent docs across multiple types.
npx skills add https://github.com/clouseryan/agentic-skills --skill docs-agent
Please help me install this Agent Skill. Skill: docs-agent Source: https://github.com/clouseryan/agentic-skills/tree/main/dev-team/docs Command: npx skills add https://github.com/clouseryan/agentic-skills --skill docs-agent
Documentation debt slows teams; this skill generates and maintains consistent project documentation across READMEs, API docs, changelogs, inline comments, architecture docs, and runbooks.
Audit the repository’s documentation and generate a prioritized plan for updates.
High-intent search queries and answers about installing and using this skill.
To audit project documentation, analyze existing READMEs, API references, and inline docs to identify gaps, outdated information, and style inconsistencies. This process generates a prioritized update plan to systematically resolve documentation debt across repositories.
The best way to generate consistent READMEs and API references is to apply an automated workflow that matches your project style and ADRs. This ensures consistent documentation structure and content across all modules and repositories.
Yes, you can align changelogs and runbooks with architecture decision records by validating generated content against established ADRs. This ensures all generated runbooks and changelogs accurately reflect your architectural standards and constraints.
Documentation generation works for inline comments and ADRs by processing source code and project context. It automatically produces inline documentation and architecture decision records while validating accuracy and consistency across the software project.
To maintain software documentation during codebase updates, run an end-to-end generation workflow that audits modified modules and updates inline docs, changelogs, and runbooks. This maintains consistency and prevents documentation debt from accumulating.
Generated documentation lacks consistency across repositories when it is not validated against a unified project style or ADRs. Applying style-matching and accuracy validation during the generation workflow ensures consistent documentation output across all modules.
EmpoweredHouseAnalyze source files to extract structure and behavior for spec generation.
theodrosyimerGenerate a browsable API documentation website from an OpenAPI specification.
mrgeoffrichRebuild API documentation and audit permissions from source code.
nobe4Enforce plain language and grug principles to produce concise AI responses.
