document-release

Automatically update documentation after a release by diffing the base branch against shipped changes and applying targeted updates to README.md, ARCHITECTURE.md, CONTRIBUTING.md, CLAUDE.md, and CHANGELOG.md. The skill enforces editorial polish, consistency, and traceability across all modified docs.

Keeping project docs in sync involves reading the post-merge diff, cross-referencing it with existing documentation, and rewriting stale sections to reflect what shipped. This skill automates that reconciliation, cleans up lingering TODOs, and optionally bumps the VERSION file.

Yes, you can polish CHANGELOG.md and bump VERSION simultaneously. The skill reads the shipped diff, applies editorial polish to the changelog for consistency, optionally increments the VERSION file when changes warrant it, and preserves full changelog history and traceability.

No dependencies or components are required to run this documentation sync tool. It operates independently by reading the base branch diff and applying editorial updates directly to core project docs without needing external libraries or frameworks.

Diffing the base branch works by comparing the shipped code changes against the main branch, identifying relevant updates, and applying those changes contextually to README.md and ARCHITECTURE.md. Risky changes are surfaced separately for user approval before any doc modifications are committed.

Run post-ship documentation updates instead of manual editing when a PR ships and multiple core docs need reconciliation. It prevents drift by automatically cross-referencing diffs with README, ARCHITECTURE, CONTRIBUTING, CLAUDE, and CHANGELOG files, which is error-prone when done manually.