document-release

To automate post-ship documentation updates, this Skill reads project docs, cross-references diffs, and updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md files to accurately reflect what shipped.

Yes, you can update your CHANGELOG and clean up TODOS when a release ships. The workflow polishes the CHANGELOG voice and removes completed TODOS based on the latest merged diffs.

Keeping README and ARCHITECTURE docs in sync with merged code changes requires cross-referencing diffs against existing project files. This workflow automates that process using Bash, Read, Write, Edit, and Grep tools.

No external dependencies or specific components are required to run this workflow. It operates autonomously using a guided process with built-in tools like Glob, Grep, Bash, and AskUserQuestion.

Yes, you can bump the VERSION file as part of your post-release documentation workflow. The process optionally increments the VERSION number when appropriate after reading and cross-referencing shipped diffs.

You should use an automated documentation workflow instead of manual updates when you need to consistently synchronize README, ARCHITECTURE, and CONTRIBUTING files with shipped diffs immediately after PR merges to prevent documentation drift.