document-release

Automate post-ship documentation updates by cross-referencing shipped git diffs against project files. This process aligns README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to accurately reflect the latest merged changes.

Keeping a CHANGELOG and README aligned with shipped changes requires cross-referencing git diff outputs. This approach polish CHANGELOG language and updates core project documentation to match the shipped state.

Clean up stale TODOs and bump project versions by running a post-release synchronization process. This cross-references shipped diffs to tidy TODOs, polish the CHANGELOG, and optionally apply a version bump.

Yes, updating CLAUDE.md and CONTRIBUTING files automatically based on git diffs is possible. The process uses Bash, Read, Write, Edit, Grep, and Glob tools to cross-reference changes and apply documentation updates.

To fix post-ship documentation drift, cross-reference the actual shipped diffs against project docs. This updates README, ARCHITECTURE, and CONTRIBUTING files to reflect reality and cleans up stale TODOs.

No external dependencies are required for this documentation alignment approach. It relies solely on standard git diff output and access to docs files, using built-in tools like Bash, Read, Write, Edit, Grep, and Glob.