document-release

To automatically update documentation after a PR merge, you can use a post-ship docs automation skill that scans project diffs and updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to reflect the shipped changes with minimal manual edits.

Post-ship documentation drift occurs when shipped code changes are not reflected in project docs. Prevent it by running an automated diff-analysis process after code shipments to sync guidance, polish changelog language, and clean up TODOS across project files.

Yes, you can automatically bump the version in your documentation. Automated post-ship docs tools can proactively suggest and perform a version bump in your project files when the scanned code diffs warrant a version increment.

To keep your CHANGELOG and TODOS aligned with shipped code changes, trigger an automated documentation sync process after PR merges. This polishes changelog wording, tidies TODOS for clarity, and ensures frontmatter-driven metadata is respected.

Yes, automated docs-sync processes can respect existing frontmatter-driven metadata. When scanning diffs and updating project files like CLAUDE.md and README, the tool enforces that your established frontmatter metadata rules are maintained.

You should run a documentation alignment process immediately after PR merges or code shipments. Triggering the diff-analysis at these points ensures your README, ARCHITECTURE, and CONTRIBUTING files reflect reality before further development occurs.