document-release

To automatically update documentation after a git merge, you can use a post-ship workflow that cross-references the PR diff to sync changes into README, ARCHITECTURE, and CONTRIBUTING files. This ensures your repository docs reflect the latest shipped code without manual edits.

The best way to keep markdown docs in sync with shipped code is to automate the cross-referencing of git diffs against your repository documentation. This approach updates key markdown files and polishes the changelog voice to match the exact release details.

To clean up TODOS and polish changelog entries after a release, an automated documentation workflow reads the shipped diff, updates pending TODOS, and refines the changelog voice to accurately reflect the completed work.

Yes, you can automatically bump the version number in your repository after merging a PR. A post-ship documentation workflow can optionally update the VERSION file to align with the newly shipped code changes.

Yes, post-ship documentation automation works with CLAUDE.md files. The workflow reads the shipped diff and syncs updates across standard markdown docs, explicitly including CLAUDE.md to ensure your project context stays current.

You should use an automated workflow to update repository documentation when you want to prevent post-ship docs from drifting out of sync with shipped code. It is ideal for cross-referencing git diffs, polishing changelogs, and bumping versions immediately after a release.