document-release

Sync documentation across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md by reading project diffs and applying shipped changes. This keeps distributed project docs aligned with the codebase after merges.

Post-ship documentation drift occurs when distributed project docs become outdated after code changes. Automated syncing reads project diffs and updates core documentation artifacts to reflect exactly what shipped, maintaining alignment without manual intervention.

Polish changelog voice and clean up TODOs by running a post-ship docs workflow that reads project diffs. It automatically refines changelog text and updates task lists to reflect the current state of merged code changes.

Yes, you can bump version numbers and surface changes in PR bodies. The workflow provides automated guidance on whether a version bump is appropriate and how to accurately represent shipped changes within pull request descriptions.

This documentation sync approach works for repositories with multiple documentation artifacts. It updates distributed files like README and ARCHITECTURE simultaneously, supporting teams that maintain proactive documentation hygiene across multi-file projects.

You should not use automated diff-based documentation updates for repositories lacking multiple documentation artifacts or post-merge maintenance needs. It is designed for projects requiring consistent changelog voice and task list updates across distributed core files.