document-release

Automating documentation updates after a git release involves validating code diffs against existing docs and synchronizing project files like README.md and ARCHITECTURE.md. This ensures your documentation accurately reflects the shipped changes without manual review.

Post-ship documentation alignment is the process of cross-referencing git history diffs to update project documentation after features merge. It ensures cross-document consistency across README, CONTRIBUTING, and CHANGELOG files to match the exact code that shipped.

Keeping README and ARCHITECTURE docs consistent requires inspecting git history to validate diffs against documentation files. Synchronizing these files after feature merges ensures project rules and architecture descriptions accurately reflect the latest shipped changes.

Yes, polishing changelog voice and cleaning up TODOs is supported during the documentation alignment process. It cross-references diffs to update the CHANGELOG with a consistent voice while simultaneously cleaning up outstanding TODOs across project docs.

You need to synchronize CLAUDE.md and CONTRIBUTING.md during release cycles or after feature merges to maintain cross-document consistency. This ensures project rules and contribution guidelines remain aligned with the shipped codebase.

The best way to sync multiple project docs is to run a post-ship workflow that inspects git diffs and automatically updates README, ARCHITECTURE, and CONTRIBUTING files. This approach ensures cross-document consistency across all project documentation.