document-release

To automate post-ship documentation updates, sync shipped code changes across project files like README and ARCHITECTURE. This ensures your docs reflect the latest release by deriving updates directly from shipped diffs.

Keeping a changelog and README in sync with merged code requires cross-referencing shipped changes against existing docs. You can polish changelog language, clean up pending TODOS, and update project files to prevent documentation drift after merges.

Preventing documentation drift after merging PRs requires reading project docs and cross-referencing them with shipped changes. This process updates files like CONTRIBUTING and CLAUDE.md based on the actual code diff.

You can automatically bump the version and polish the changelog after shipping by applying post-ship documentation updates. This process cleans up pending TODOS and refines changelog voice while syncing project files with the released code.

Post-ship documentation sync works for CLAUDE.md and ARCHITECTURE files by reading these project docs and updating them to reflect shipped changes. This ensures all key project documentation stays aligned with the released codebase.