document-release

To keep documentation in sync after a git release, you can automate the process by scanning code diffs and propagating updates across key project files like README, ARCHITECTURE, and CHANGELOG. This ensures shipped code and docs remain consistent.

Documentation drift occurs when shipped code changes are not reflected in project docs. Prevent drift by automating post-ship housekeeping tasks to scan repository diffs and apply corresponding updates across README, CONTRIBUTING, and CLAUDE.md files.

Yes, you can automatically update the CHANGELOG and bump the project version when merging a PR. The process detects changes from merges, polishes the CHANGELOG, cleans up TODOS, and optionally applies a version bump to reflect shipped changes.

Yes, automated docs sync works with CLAUDE.md and ARCHITECTURE files. The process specifically targets these files alongside README, CONTRIBUTING, and CHANGELOG to apply updates detected from diffs, ensuring comprehensive documentation consistency across your repository.

The best way to automate post-ship housekeeping is using Bash scripts that read, write, and edit repository files based on scanned diffs. This approach quickly propagates updates across key docs and optionally bumps the project VERSION.