document-release

You can automate documentation updates post-ship by cross-referencing your change log against project files. This process updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files while refining the CHANGELOG to ensure code-to-doc sync.

Documentation debt refers to missing or outdated project documentation. The skill identifies this debt by performing cross-document consistency checks after shipping, then reports any missing or outdated documentation directly to the PR body for tracking.

Yes, you can handle version bumps and CHANGELOG updates together. The skill optionally handles version bumps in documentation files and polishes the CHANGELOG voice for clarity during the automated post-ship update process.

Automated documentation maintenance requires Bash, Read, Write, Edit, Grep, Glob, and AskUserQuestion tools for execution. These dependencies support cross-document consistency checks and file updates across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files.

The best way to keep README and ARCHITECTURE files synced is to perform cross-document consistency checks against the change log. This ensures all relevant documentation files match the latest shipped code and automatically highlights remaining documentation debt.