docs:update-docs

To automate documentation updates for local code changes, you analyze uncommitted diffs or the latest commit to locate documentation-impacting edits. The system coordinates analysis and tech-writer agents to generate targeted, maintainable updates for README files, JSDoc, and API references.

Multi-agent documentation generation works by orchestrating analysis agents to extract documentation-impacting changes and tech-writer agents to group, prioritize, and produce content. This ensures module README updates and API reference changes are accurately maintained after a refactor.

Change-driven documentation discovery is the process of analyzing uncommitted changes or the latest commit to locate edits requiring doc updates. You need it when projects accumulate undocumented code changes and outdated guides to prevent documentation bloat and drift.

Yes, you can use this to update JSDoc and generated API documentation together. It applies to repositories with docs directories, README files, JSDoc, or generated API documentation, grouping tasks by documentation area to coordinate comprehensive updates.

The best way to audit documentation quality after updating code is to run quality review agents that verify examples, links, and style. This ensures targeted content generation avoids bloat and drift while maintaining accurate index documents and module READMEs.

Yes, this documentation update workflow works with both uncommitted local changes and the latest commit. It performs discovery of documentation infrastructure and extracts documentation-impacting changes to produce prioritized tasks and suggested file updates.