document-release

Automating post-merge documentation updates involves reading project docs, cross-referencing the code diff, and updating relevant files. This Skill targets software development workflows to maintain accurate, up-to-date project documentation automatically after a ship.

Keeping README and Architecture files consistent requires cross-file consistency checks against the shipped codebase. This Skill reads documentation, cross-references code diffs, and updates relevant files to ensure all project documentation aligns without factual inconsistencies.

A post-merge documentation update tool handles CHANGELOG generation by refining the voice of the CHANGELOG for better readability and engagement. It reads the project documentation and code diff to polish entries after the feature branch is merged.

You can update CONTRIBUTING and CLAUDE.md files automatically alongside the codebase. This Skill updates README, Architecture, CONTRIBUTING, and CLAUDE.md files to reflect recent code changes and ensures cross-file consistency after merging.

You need bash, read, write, edit, grep, glob, and askuserquestion to run this automated post-ship documentation update process. These dependencies are required for the tool to read diffs, search files, and apply updates to the project documentation.

You should avoid using an automated tool for post-merge documentation updates when the code diff lacks structural changes impacting documentation, or when manual review is required for highly sensitive architectural changes before updating the project files.