document-release

Automatically update README and CHANGELOG after shipping by cross-referencing the git diff. The Skill reads project docs, reflects shipped changes across key files, polishes CHANGELOG voice, and cleans up TODOS.

Post-ship documentation sync aligns README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md with shipped code changes. You need it immediately after a PR merge to prevent documentation drift and keep the CHANGELOG accurate.

Polish CHANGELOG voice and clean up TODOS by analyzing the shipped diff and updating documentation files. The Skill refines the CHANGELOG narrative tone and removes obsolete TODO items to reflect the current codebase state.

Yes, you can automatically bump the VERSION file when updating project documentation. The Skill optionally increments the version number alongside syncing README, ARCHITECTURE, and CONTRIBUTING files when asked to run post-ship docs.

Yes, automated documentation sync works without external dependencies. The Skill reads all project docs and cross-references the diff internally to update README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md without requiring additional packages.

The best way to keep architecture documentation in sync is cross-referencing the code diff against existing docs. The Skill updates ARCHITECTURE.md and other key files to accurately reflect what shipped, eliminating manual post-ship updates.