document-release

You can automate post-ship documentation alignment by scanning all project docs and cross-referencing diffs. This updates README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md to accurately reflect the latest shipped features and modifications.

Post-ship documentation alignment syncs project files with released code changes. You should apply it immediately after a PR is merged to prevent documentation drift and reduce maintenance toil across cross-document references.

You can polish CHANGELOG voice and clean up TODOS by running an automated post-ship scan over your repository. This process refines release notes and optionally bumps the VERSION file to match the new state.

Yes, you can sync project documentation automatically using Bash-based tooling. The process uses Read, Write, Edit, Grep, and Glob operations to scan diffs, apply changes to relevant docs, and report completion without manual intervention.

Automating documentation updates requires full repository access and depends on Bash-based tooling. It operates post-ship by cross-referencing diffs, meaning it requires an existing repository state and cannot generate documentation for uncommitted or unmerged code.