document-release

Automating post-ship documentation updates involves scanning code diffs to sync project docs. This Skill aligns README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md with shipped changes while polishing the CHANGELOG and cleaning up TODOS.

Diff analysis for syncing documentation works by cross-referencing shipped code changes against existing files. It reads project docs, identifies mismatches with the diff, and updates content to accurately reflect the new release state.

Keeping a changelog and README updated after shipping is best handled by an automated workflow. This Skill cross-references diffs to update docs and polishes the CHANGELOG voice to ensure consistency across all core files.

Yes, you can automatically bump the version number when updating documentation. This Skill optionally bumps the VERSION file as part of the post-ship sync workflow, alongside updating README, ARCHITECTURE, and CONTRIBUTING files.

This documentation workflow does not require external dependencies. It operates independently using built-in scripting capabilities like Bash, Read, Write, Edit, Grep, Glob, and AskUserQuestion to orchestrate the syncing process.

You should run a post-ship documentation sync immediately after shipping new changes. Use it when asked to update the docs or sync documentation, ensuring README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md reflect the latest code state.