document-release

To update project documentation to match a new code release, this Skill cross-references shipped diffs against README.md, ARCHITECTURE.md, and CONTRIBUTING.md, automatically applying safe, idempotent edits to synchronize the docs with the release state.

Polishing a CHANGELOG after shipping involves refining the release voice, cleaning up TODOS, and optionally bumping the version. This Skill automates that process by reading project diffs and applying those formatting updates directly.

Updating post-ship docs requires knowledge of the repository structure to safely navigate and modify files. This Skill uses Bash, Read, Write, Edit, and Grep to perform safe, idempotent updates based on that underlying structure.

You can synchronize CLAUDE.md and ARCHITECTURE.md automatically after a PR merge by running this Skill. It reads the shipped changes and updates these specific project files to reflect the latest release state without manual rework.

You should run documentation synchronization for post-ship drift immediately after a PR is merged or code is shipped. This prevents documentation from falling out of alignment with the actual codebase changes over time.

Automating documentation updates with a diff relies on cross-referencing project files and requires understanding the repository structure. It performs safe, idempotent updates but may require user input via AskUserQuestion for complex structural changes.