document-release

Automate post-ship documentation updates by cross-referencing git diffs with existing docs to synchronize README, ARCHITECTURE, and CONTRIBUTING files with shipped code changes. It reads markdown files and applies targeted updates to reflect new features, APIs, or architecture modifications.

Keeping README and changelog consistent involves multi-file synchronization across your project, analyzing recent git diffs to update documentation sections and polishing the CHANGELOG voice. This automated approach ensures docs match shipped code by updating all related files in one pass.

Yes, you can automatically bump VERSION files to match a new release state and remove completed TODOs from the codebase. This cleanup happens during the documentation synchronization pass, ensuring your versioning and task tracking stay current with merged code.

Yes, git repository access is required to cross-reference diffs and apply targeted updates. The Skill needs read and write access to both markdown documentation files and the git repository to identify code changes and update ARCHITECTURE or CLAUDE.md files accordingly.

Multi-file documentation synchronization works across multi-file codebases by updating README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md in one pass. It targets documentation sections referencing modified features, APIs, or architecture to maintain consistency regardless of project scale.