document-release

To update README and CHANGELOG after merging, run the document-release skill which reads git diffs and applies factual edits to documentation files automatically. It scans branch changes and updates file paths, counts, and factual items across README, ARCHITECTURE, and CHANGELOG.

Documentation drift is the gap between shipped code and project docs. You prevent it by running a post-ship sync that reads branch diffs, applies factual updates to README and CHANGELOG, and prompts for risky narrative edits requiring human approval.

Yes, you can polish CHANGELOG entries without rewriting history by using a guided documentation sync tool. It refines wording in existing entries, preserves the original record, and applies clear factual edits without deleting past content.

Diff-aware documentation update does not auto-apply version bumps or large narrative changes. It uses a guided approval system that applies clear factual edits automatically but prompts you for version bumps, narrative changes, and other risky decisions requiring human review.

To sync TODOS.md and ensure cross-doc consistency, run a documentation sync skill that moves completed TODOs when obvious and flags discoverability gaps between README and CLAUDE.md. It scans diffs to resolve inconsistencies across all repository documentation files.

The best way to update ARCHITECTURE.md and CONTRIBUTING.md after a release is to use an automated diff analysis tool that reads the branch diff against the base branch and applies factual edits to documentation. This prevents drift between shipped code and project docs.