document-release

Automating post-ship documentation updates involves cross-referencing the shipped diff against existing project docs. This skill reads the changes and automatically updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to accurately reflect the new release.

The best way to sync docs with a shipped code diff is using an automated post-ship doc synchronization process. It cross-references the diff to update README and ARCHITECTURE, while polishing the CHANGELOG language to match the release notes.

Yes, you can bump the VERSION and clean up TODOs during a post-ship doc sync. The process optionally aligns the VERSION with the release and tidies up TODOs alongside updating core documentation like CONTRIBUTING and CLAUDE.md.

Cross-referencing a shipped diff works by analyzing the code changes and mapping them to existing documentation. It then automatically rewrites the relevant sections in README, ARCHITECTURE, and CLAUDE.md to ensure the docs match what actually shipped.

No, you do not need to manually trigger documentation updates after a PR merge. You can simply request to "update the docs" or "sync documentation", and the skill automatically reconciles the docs and changelogs with the latest release.