document-release

To automatically update documentation after a release, you need a tool that reads the git diff from shipped changes and syncs core project files. This skill updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md to reflect the latest code state.

The best way to keep a CHANGELOG accurate is to automate the refinement process during post-ship updates. This skill reads the current git diff, polishes the CHANGELOG wording, and cleans up outstanding TODOS to ensure project documentation is easy to understand.

Yes, you can automatically bump the VERSION file when shipping code changes. This skill optionally increments the VERSION file during the documentation sync process if the workflow allows it.

Doc-sync automation handles architectural and contributing guidelines by reading the shipped git diff and updating ARCHITECTURE.md and CONTRIBUTING.md. This ensures all core documentation accurately reflects the newly merged code structure and workflows.

You need to run documentation updates after a git merge when shipped changes alter the codebase structure or behavior. This skill proactively suggests syncing docs after PR merges to prevent documentation drift across core project files.