document-release

To automatically update documentation after a code merge, you need a tool that cross-references project docs against the current code diff. This skill reads your README, ARCHITECTURE, and CONTRIBUTING files to identify and patch stale content based on recently shipped changes.

Keeping documentation in sync with git diff changes requires analyzing the shipped code against existing docs. This skill automates that synchronization by reading all project documentation files and applying updates to reflect the actual code modifications.

Changelog polishing works by refining the text voice for consistency and cleaning up outdated TODOS across the codebase. This skill performs these post-ship documentation updates alongside reconciling README and ARCHITECTURE files with the merged code.

Yes, you can automatically bump version numbers after deployment. This skill includes an optional feature to increment VERSION files, ensuring your project versioning matches the new release alongside the updated documentation.

Yes, this documentation update tool works without external dependencies. It operates independently to read project files, compare them against the code diff, and apply necessary updates to your documentation and changelogs.

You need to update CLAUDE.md files after shipping code when the merged changes alter project workflows or architecture. This skill cross-references CLAUDE.md against the current code diff to identify and fix any stale content.