document-release

Automate documentation updates after a code release by cross-referencing code diffs with project docs to update stale README, ARCHITECTURE, and CHANGELOG files automatically. This Skill performs the post-ship documentation sweep to maintain accuracy without manual effort.

Documentation drift occurs when shipped code changes leave project docs out of sync. Detect architecture diagram drift by cross-referencing recent code diffs against existing markdown files to identify and update outdated structural references.

Keep your CHANGELOG and README in sync with merged PRs by reading project markdown files, detecting outdated sections, and updating them to match what actually shipped. It also polishes the CHANGELOG voice and surfaces documentation debt in the PR body.

Map documentation coverage using the Diataxis framework automatically by building a reference, how-to, tutorial, and explanation coverage map from project docs, then cross-referencing it against recent code changes to spot gaps.

Yes, this documentation synchronization tool works without external dependencies. It reads your existing project markdown files, analyzes code diffs, and generates documentation debt reports directly within your software engineering workflow.

The best way to surface documentation debt during PR review is to generate an automated debt report directly in the PR body. This provides immediate visibility into stale content and missing architecture updates for reviewers.