document-release

Automating post-ship documentation updates involves reading shipped diffs to reconcile changes across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files. This ensures core project docs accurately mirror released code changes without manual editing.

Keeping a CHANGELOG and project docs in sync requires reading shipped code diffs and applying those updates across core documentation files. This process polishes CHANGELOG wording, tidies TODOS, and optionally bumps the VERSION for traceability.

Diff-based documentation reconciliation works by analyzing code changes from a shipment or PR merge, then applying those updates deterministically to README, ARCHITECTURE, and CONTRIBUTING docs. This safe update flow ensures consistency and traceability across project files.

Yes, you can automatically bump the VERSION file when doc-related changes are released or after a PR merge. This optional step occurs alongside synchronizing README, ARCHITECTURE, and other core docs to maintain accurate version tracking.

No external dependencies are required to synchronize post-ship documentation. The process relies on deterministic tooling and safe update flows built into the skill to read diffs and apply updates across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md.

Post-ship documentation maintenance becomes error-prone because manually updating README, ARCHITECTURE, and CONTRIBUTING files to reflect shipped changes invites inconsistencies. Automating diff reconciliation ensures core docs, CHANGELOG wording, and TODOS stay perfectly aligned with the released code.