document-release

To update markdown documentation after a git commit, you can cross-reference git diffs against project files to selectively edit README, ARCHITECTURE, and CHANGELOG docs, ensuring they accurately match the shipped code.

Keeping a CHANGELOG consistent with merged PRs involves parsing markdown files and refining existing entries based on git diff analysis, maintaining factual accuracy and voice consistency without rewriting project history.

Cross-referencing git diffs against project docs prevents documentation drift by analyzing code changes and applying selective file editing to markdown files, ensuring every document accurately reflects what actually shipped.

Yes, you can automatically mark completed TODOs and flag new ones in markdown files by analyzing shipped changes from git diffs and updating the documentation to reflect the current project state.

Post-ship documentation updates do work for CLAUDE.md and CONTRIBUTING files, reading all project docs and cross-referencing them with git diffs to maintain factual accuracy across every markdown file in your project.

You should avoid automating README and ARCHITECTURE doc updates when a project lacks git diff history or when documentation requires manual narrative restructuring that exceeds selective markdown parsing and editing capabilities.