document-release

Automate post-release documentation updates by scanning code diffs and synchronizing core project docs like README and ARCHITECTURE to match shipped changes. This reduces manual churn by detecting drift and surfacing documentation debt directly in PR bodies for review.

A Diataxis coverage map categorizes documentation into reference, how-to, tutorial, and explanation types to clarify coverage. Building this map during documentation sync helps identify gaps and ensures all shipped changes are accurately reflected across the appropriate explanatory formats.

Detect architecture diagram drift by cross-referencing project diffs against existing documentation after a release. The skill scans these diffs to identify mismatches between shipped code changes and the diagrams in your ARCHITECTURE docs, surfacing them for review.

You can update CONTRIBUTING and CLAUDE.md files automatically by running the skill after a release. It scans your project diffs and applies localized text-editing capabilities to ensure these specific standard docs reflect the actual shipped changes.

You do not need external dependencies to synchronize changelogs and bump versions. The skill operates with zero dependencies, requiring only local access to project docs and standard text-editing capabilities to polish changelog language and optionally bump the VERSION.

Surface documentation debt in PR bodies by scanning post-ship diffs and identifying outdated TODOS or unpolished changelog entries. The skill cleans up these inconsistencies and compiles the remaining debt into the PR body for immediate review.