document-release

Automate post-ship documentation updates by scanning project docs and cross-referencing diffs to ensure alignment with shipped changes. This skill automatically updates README, ARCHITECTURE, CONTRIBUTING, and CLAude.md files to reflect the latest release state.

Yes, you can bump the VERSION and polish the CHANGELOG after merges. The skill cleans up TODOS, refines the changelog voice, and optionally updates the version number to ensure diffs stay synchronized across all project documentation.

The best way to keep markdown docs synchronized is using diff detection to cross-reference shipped changes against existing documentation. This skill automatically edits markdown frontmatter and sections across README, ARCHITECTURE, and CONTRIBUTING files.

No external dependencies are required, but you need local repo file access. The skill can be configured via allowed-tools like Bash, Read, Write, Edit, Grep, Glob, and AskUserQuestion to perform automated markdown edits and diff scanning.

Diff detection works by scanning project docs and cross-referencing the code diff to identify drift. It then applies automated edits to markdown sections and frontmatter, ensuring the README, ARCHITECTURE, and CONTRIBUTING files accurately reflect the shipped state.