document-release

Automate post-merge documentation sync by scanning shipped diffs and updating README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md to reflect shipped changes. This aligns project docs automatically after a PR is merged or code is shipped.

Polish changelog language after shipping by refining changelog entries to match the actual release voice. This workflow reads shipped changes and updates Markdown files in place to ensure the changelog reflects the released state accurately.

Yes, you can bump VERSION across multiple docs after a ship. This workflow optionally applies version bumps based on configured guidelines, tidies TODOS, and ensures all documentation files remain aligned with the shipped state.

Clean up TODOS in documentation after merging a PR by running a post-ship workflow that reads repository docs, updates Markdown files in place, and tidies leftover TODOS to keep all project documentation aligned with the merged changes.

No specific dependencies are required to update Markdown docs in place after a release. This workflow requires only the ability to read and diff repository docs, update Markdown files, polish language, and optionally bump VERSION.

Run a post-ship docs synchronization workflow immediately after a PR is merged or code is shipped. This ensures README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md reflect the shipped state and prevents documentation drift.