document-release

To update project documentation after shipping, this skill reads code diffs and applies matching changes to README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files. It scans the shipped diff, validates the changes, and synchronizes all related docs automatically.

Keeping CLAUDE.md and CHANGELOG files in sync after a PR merge involves reading the latest diffs and applying updates across all project docs. This skill polishes CHANGELOG language, cleans up TODOS, and updates CLAUDE.md to accurately reflect what shipped.

Yes, you can automatically bump the VERSION file as part of post-ship documentation synchronization. The skill optionally bumps the VERSION file alongside updating README and other docs to maintain project hygiene after a shipment.

You should use a post-ship documentation synchronization tool whenever a PR is merged or code is shipped and your project docs risk drifting. It cross-references the diff to update README, ARCHITECTURE, and CONTRIBUTING files to match the new codebase.

No external dependencies are required to scan diffs and update documentation. The skill operates autonomously using standard Bash, Read, Write, and Edit tooling to scan code diffs, validate changes, and apply updates across project documentation files.

To clean up TODOS and polish CHANGELOG language after a release, the skill scans the shipped diff and proactively refines the CHANGELOG text. It removes stale TODOS and ensures all documentation reflects the current state of the project.