document-release

You can sync your CHANGELOG and core docs to your latest shipping changes by running an automated post-ship docs update. This process reads the diff, polishes the changelog voice, tidies TODOS, and optionally bumps your VERSION file.

Keeping documentation aligned after a PR requires cross-referencing the shipped diff and updating your README, ARCHITECTURE, and CLAUDE.md files accordingly. This prevents documentation drift and ensures user-facing surfaces match shipped code.

Changelog and versioning automation handles post-ship documentation by reading repository diffs, polishing the CHANGELOG voice, tidying TODOS, and optionally bumping the VERSION file alongside updating core documentation.

Yes, you can automatically update CLAUDE.md and CONTRIBUTING files based on your git diff. Automated documentation tools cross-reference shipped changes to apply repository-wide edits with safe validations across these specific files.

No external dependencies are required to automate repository-wide documentation edits. The process orchestrates safe validations and file modifications using built-in tools like Bash, Read, Write, Edit, Grep, and Glob.

You should avoid automating post-release documentation sync if your project lacks a clear diff to cross-reference or if your documentation requires manual narrative adjustments that exceed simple changelog polishing and TODO tidying.