document-release

To update project documentation after a pull request merge, you can automate the process by reading code diffs to sync README, ARCHITECTURE, and CONTRIBUTING files with the shipped changes, ensuring docs reflect the latest state without manual edits.

Post-ship documentation automation aligns project docs with the latest shipped changes by analyzing diffs. It proactively suggests updates to README, ARCHITECTURE, and CONTRIBUTING files after code shipments, ensuring documentation matches the deployed state.

You can sync a CHANGELOG with a version bump by using diff analysis to polish the changelog voice and optionally bump the VERSION file, ensuring release notes and versioning stay consistent with the shipped code.

Yes, you can automatically clean up TODOS after shipping code by analyzing the shipped diff. This post-ship docs update process scans completed changes and removes or updates resolved TODO items to match the current codebase state.

Yes, diff analysis works for updating CLAUDE.md files. It cross-references the shipped code changes against existing project documentation and applies necessary updates to CLAUDE.md to ensure it matches the new project architecture.

You should avoid automated documentation updates when changes are purely cosmetic or do not affect project behavior, as diff analysis targets architectural or functional modifications that impact README, ARCHITECTURE, or CONTRIBUTING files.