document-release

To keep documentation aligned with shipped code, analyze git diffs after releases to identify drift across README.md and ARCHITECTURE.md, then apply targeted updates through a constrained workflow that preserves formatting and links.

Updating CHANGELOG.md relies on analyzing historical git data and feature diffs after a release. The process inventories committed changes, detects omissions in the changelog, and applies refined text updates to reflect the new version.

Yes, you can synchronize documentation across repositories after releases. The process inventories docs like TODOS.md and docs/ directories, analyzes diffs for feature changes, and commits updates to ensure consistency with the codebase.

The best way to detect stale documentation is running a diff analysis against the codebase post-release. This identifies divergences between shipped features and existing READMEs, architecture notes, and changelog omissions.

Yes, updating docs through diff analysis preserves formatting. The workflow applies documentation updates through a constrained process specifically designed to maintain existing markdown structures, formatting, and links.

Yes, repository access to historical git data is required. This access allows the inventory and diff analysis processes to verify feature changes and accurately apply documentation updates to reflect the latest shipped code.