document-release

To keep documentation in sync after a release, apply diff-aware updates to README and architecture docs by reading shipped changes and modifying the relevant files to reflect the released code, eliminating drift between living docs and shipped code.

The best way to automate changelog polishing and version bumping is using a post-ship workflow that reads diffs, updates contribution guides, refines the changelog voice, and optionally bumps the project version during the documentation update process.

Yes, you can update CLAUDE.md and contribution guides automatically after PR merges by applying cross-repo diff-aware updates that read the shipped changes and modify the specified documentation files to reflect the merged code.

Yes, this documentation update approach works across different repositories because it applies diff-aware updates to key docs after PR merges, releases, or ship events regardless of the specific repository structure.

You need to update project documentation after shipping code changes when you want to prevent drift between your living docs and the released code, ensuring developers and reviewers avoid confusion caused by outdated READMEs or architecture docs.