document-release

Automate documentation updates by running a post-ship workflow that reads release diffs and updates README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, and CHANGELOG to reflect shipped changes. This ensures project docs automatically stay in sync with merged code without manual edits.

Keeping CHANGELOG and README in sync with merged PRs is done by reading the diff from the latest ship and cross-referencing changes across key project docs. This automated diff-analysis approach applies updates to reflect the latest release consistently.

Yes, you can automatically bump the version when appropriate during the documentation update process. The workflow reads shipped diffs, aligns project docs, tidies TODOS, and optionally applies a version bump to keep all documentation consistent with the release.

Yes, this documentation automation works without external dependencies. It operates independently after a PR is merged or code is shipped, reading diffs and updating project docs like README and CHANGELOG without requiring additional setup or installed packages.

Run post-ship documentation alignment immediately after a PR is merged or code is shipped. This prevents documentation drift by scanning the release diff and applying updates across README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, and CHANGELOG before the next development cycle begins.

Automated diff-analysis updates README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, and CHANGELOG files. It reads the diff from the latest ship, cross-references the changes, and applies targeted updates to keep these key project docs consistent with the released code.