document-release

To keep documentation in sync after a release, you can trigger a post-ship workflow that analyzes code diffs between base and HEAD to identify outdated documentation drift and apply automatic updates.

Documentation drift occurs when docs become outdated after code changes. You detect it by running a diff-driven audit that compares your base branch against HEAD to identify missing or outdated references.

Yes, the workflow automatically aligns CHANGELOG, READMEs, and reference files by applying straightforward corrections identified during the diff analysis, ensuring cross-doc consistency.

You prepare a PR-ready documentation summary by auditing files, formatting changes, and generating a governance summary that highlights applied corrections and risky narrative edits requiring review.

You should manually review risky narrative edits when the governance workflow detects potentially impactful changes to documentation context, prompting you to verify updates before finalizing the PR.