document-release

To sync README and CHANGELOG after a release, you can run the document-release workflow to automatically reconcile post-ship docs. It applies a read-diff then rewrite workflow to align README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md with shipped changes.

The best way to update project documentation to reflect shipped changes is using an automated documentation sync tool. This skill polishes the CHANGELOG language, tidies TODOS, and aligns core docs with the released state through a traceable read-diff and rewrite process.

To polish CHANGELOG language and clean up TODOs after shipping, you can run an automated docs-sync workflow. It rewrites the changelog to match the released state and cleans up outdated TODOs while generating traceable logs of all modifications.

Yes, you can automatically bump the VERSION file when updating post-release documentation. The skill optionally applies a version bump to reflect the release alongside reconciling README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md.

Post-ship documentation reconciliation handles missing sections or manual edits by applying an automated read-diff and rewrite workflow. It specifically manages these common edge cases to ensure README.md, ARCHITECTURE.md, and CONTRIBUTING.md align accurately with shipped changes.

You should use an automated docs-sync workflow for post-release documentation when applying PR merges or running release workflows. It effectively aligns README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md with shipped changes, preventing documentation from lagging after ship.