document-release

The document-release skill audits documentation drift by reading project docs, cross-referencing the code diff, and updating README, ARCHITECTURE, CONTRIBUTING, CLAUDE.md, and CHANGELOG to reflect shipped changes.

A Diataxis coverage map categorizes documentation into reference, how-to, tutorial, and explanation types. The skill builds this map to identify mismatches between shipped code and documentation, ensuring comprehensive coverage of project updates.

To detect architecture diagram drift after a release, the skill cross-references the shipped diff against existing project docs and surfaces inconsistencies, including diagram drift, directly in the PR body as documentation debt.

Yes, you can automatically bump VERSION and polish CHANGELOG entries when shipping. The skill optionally bumps the VERSION file, refines the CHANGELOG voice, and cleans up TODOS during the post-ship documentation audit.

To surface documentation debt in a PR body, the skill audits all project docs against the diff, detects mismatches like architecture diagram drift, and appends a summary of this debt directly into the PR body.

No specific dependencies are required to run the document-release skill. It operates independently to read project docs, build a Diataxis coverage map, and update key documentation files based on the shipped diff.