document-release

To sync project documentation after a PR merge, the skill cross-references shipped diffs and updates key files like README, ARCHITECTURE, and CONTRIBUTING to accurately reflect the latest changes. It ensures all post-ship docs stay perfectly aligned with the codebase.

The best way to update a CHANGELOG and clean TODOS after a release is using an automated documentation update process that polishes language and removes completed items. This skill handles those optional steps while synchronizing post-ship documentation across your repository.

Cross-referencing diffs keeps README and ARCHITECTURE docs in sync by reading all project documentation, comparing it against shipped code changes, and automatically updating key files. This prevents post-ship documentation drift by ensuring every file matches the merged code.

Yes, you can bump VERSION and update CLAUDE.md when code ships. The skill optionally bumps the VERSION file when appropriate and ensures CLAUDE.md stays in sync alongside README and other key documentation files after a release.

No, this documentation update approach requires no external dependencies. It operates independently to cross-reference diffs, polish CHANGELOG language, and synchronize post-ship documentation across your repository without needing additional libraries or tools.

You should not use automated post-ship documentation synchronization for pre-ship staging or when manual narrative control over CHANGELOG language is strictly required. The skill is designed specifically for post-merge updates, proactively suggesting documentation changes after code has already shipped.