document-release

Automating changelog updates involves reading shipped code diffs and cross-referencing them with your project docs. This skill aligns README, ARCHITECTURE, and CONTRIBUTING files to reflect the shipped changes, while polishing the changelog voice and cleaning up TODOS.

Syncing README and ARCHITECTURE docs requires cross-referencing shipped diffs against existing documentation. This skill reads the project diff, updates core docs to match the release, and ensures your CLAUDE.md and CONTRIBUTING files reflect the latest codebase state.

Yes, you can bump the VERSION file automatically after a release. When running post-ship documentation updates, this skill evaluates the shipped changes and applies an optional version bump alongside updating core project files and polishing the changelog.

Cleaning up TODOS and polishing changelog voice is done by applying automated documentation updates post-release. This skill adjusts the changelog language for consistency, removes resolved TODO comments, and ensures the documentation matches the shipped diff.

Yes, this documentation update tool explicitly works with CLAUDE.md and CONTRIBUTING files. It reads these core project docs, cross-references them with the shipped code diff, and updates their content to accurately reflect the latest release changes.

Post-ship documentation updates are needed after a release or PR merge when code changes alter existing functionality. Running this skill ensures your README, ARCHITECTURE, and changelog stay synchronized with the shipped diff without manual editing.