document-release

To update documentation after a release, you can scan changed files and cross-reference the diff to update core docs like README and ARCHITECTURE.md. This skill reconciles post-ship documentation by reading, comparing, and modifying files to reflect the shipped state.

Architecture documentation drifts because post-ship docs are rarely updated to match the latest code changes. This skill detects drift by scanning changed files and cross-referencing the diff to update architecture notes accurately.

Yes, you can polish your CHANGELOG and optionally bump the version during release- or merge-driven updates. This skill refines the changelog voice and applies version bumps while updating core documentation.

The best way to surface documentation debt in a PR body is to scan project diffs and generate a concise report of what changed. This skill compares shipped changes against existing docs and highlights the debt in your PR descriptions.

You do not need specific dependencies to synchronize docs with shipped changes. This skill relies on Bash and common CLI tools to read, compare, and modify files, requiring no external packages to function.