document-release

Automating documentation updates after a code merge involves cross-referencing project docs with code changes to identify and apply updates. This process reads files like README and CHANGELOG to keep documentation in sync with the codebase.

Keeping documentation in sync with the codebase requires cross-referencing code changes against existing documentation files to detect gaps. Automated tools can read, edit, and update README, Architecture, and Contributing files to maintain alignment after shipment.

Yes, this documentation update process works with PR and MR body updates by automatically updating the pull request or merge request body with documentation changes. It also identifies gaps in documentation coverage based on the detected code changes.

Yes, you can automatically update the CHANGELOG and apply version bumps after shipping. The process detects required updates in documentation files and optionally suggests or applies version bumps to the project's VERSION file when necessary.

Yes, you need Bash, Grep, Glob, Read, Write, and Edit tools to run automated documentation updates. These tools are required to process project files, search through the codebase, and apply the identified documentation changes accurately.

Limitations of automated code sync for documentation include potential gaps in coverage detection that require manual review. The process optionally performs an additional review using Codex to ensure accuracy and completeness, but complex changes may still need human verification.