document-release

Automating documentation updates after a code shipment involves comparing code diffs with project documents to ensure accuracy and consistency across files. This Skill reads project documents, cross-references the diff, and updates README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md to match what shipped.

Keeping project documentation consistent after a PR merge requires proactively suggesting updates by cross-referencing code changes with existing docs. This approach ensures README, ARCHITECTURE, and CONTRIBUTING files reflect the shipped code while polishing the CHANGELOG voice.

Automated documentation management for post-merge code changes works by reading project files, identifying discrepancies between the diff and existing documentation, and applying targeted edits. It ensures absolute accuracy and consistency across various documentation files without manual effort.

You do not need to manually update your CHANGELOG after shipping code. This Skill automates the process by comparing code changes and polishing the CHANGELOG voice to match what shipped, ensuring high-quality documentation without manual effort.

Yes, you can update CLAUDE.md and ARCHITECTURE files automatically. The Skill specifically targets these files alongside README and CONTRIBUTING docs, cross-referencing code diffs to ensure all documentation accurately reflects the shipped project state.