document-release

To update documentation after a PR, run document-release to compare project diffs against existing docs and automatically sync README, ARCHITECTURE, and CONTRIBUTING files with the shipped code changes.

Keeping CHANGELOG and project docs in sync is done by cross-referencing shipped diffs to polish release notes, clean up TODOS, and update core documentation files to accurately reflect the latest version.

Yes, you can manage VERSION bump decisions automatically. The skill evaluates shipped changes and optionally bumps VERSIONs when appropriate to prevent documentation and release state drift.

The best way to polish release notes is to cross-reference the latest diff against project docs, which refines the CHANGELOG voice and tidies TODOS for accurate release documentation.

No specific dependencies are required to run this documentation sync tool. It operates independently to read project files, compare them to the latest ship, and update core docs.

You should avoid automatic documentation updates if your project requires manual review of release notes or if your docs are managed outside the core README, ARCHITECTURE, CONTRIBUTING, and CLAUDE files.