document-release

Automating documentation updates post-ship requires cross-referencing code diffs to modify project files. This skill updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to reflect the latest shipped code changes using a single command.

Syncing a README and CHANGELOG with a recent git diff involves analyzing the code changes and applying them to documentation. This skill cross-references diffs to refine the CHANGELOG, remove TODOs, and update README content automatically.

Bumping a VERSION file while updating architecture docs is supported by this skill through an optional version bumping feature. It simultaneously updates ARCHITECTURE documentation based on the shipped code diff to ensure version and structural consistency.

Yes, you need Bash, Glob, Grep, Read, Write, Edit, and AskUserQuestion tools to automate post-ship documentation updates. These dependencies enable the skill to execute scripts, locate files, parse diffs, and apply edits across your project.

Yes, you can update a CLAUDE.md file based on code diffs after a pull request merge. The skill specifically targets CLAUDE.md alongside README and CONTRIBUTING files to ensure all project documentation matches the newly merged code.

Limitations of automating documentation updates with code diffs include dependency on specific tools like Bash, Read, Write, and Grep. The skill focuses on README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md, meaning custom documentation files outside this set require manual updates.