doc-updater

Documentation synchronization automates updates when APIs, interfaces, or architecture change. This Skill detects code modifications, generates update proposals matching your project's style guidelines, validates changes against your documentation build process, and applies updates after confirmation—eliminating manual tracking of code-to-docs consistency.

Update documentation whenever public APIs change, new classes or functions are added, architecture shifts occur, or inconsistencies between code and docs emerge. This Skill automatically detects these scenarios and proposes targeted updates to affected sections like API references, guides, and architecture documentation without manual intervention.

Yes. The Skill integrates with your documentation build process to validate proposed changes, checking for errors and ensuring compliance with your project's documentation standards defined in `.claude/docs.md` before any updates are applied.

Automatic updates trigger on public API or interface changes, new classes, functions, or modules, architecture modifications, explicit update requests, and detected code-documentation inconsistencies. The Skill analyzes each change, identifies affected documents, and generates proposals aligned with your project's documentation format.

No. This Skill activates automatically when code changes occur and proposes updates proactively. You can also explicitly request updates by asking Claude to update documentation for specific components; manual confirmation and build verification occur before final application.

The Skill adheres to your project's specific documentation style and markup guidelines defined in `.claude/docs.md`. It generates update proposals that match your established conventions, ensuring consistency across all documentation and reducing manual formatting work.