codex-docs-change-sync

Mapping code changes to documentation updates surfaces impacted docs without editing them. It analyzes staged, unstaged, or last-commit git diffs and reports candidate files with confidence scores to guide reviewers.

No, this approach reports candidate files rather than performing automatic edits. It maps code diffs to README.md, CHANGELOG.md, and docs/* files, providing reasons and confidence scores to enable reviewer-guided updates.

You run a mapping script against your project root during docs steps. It auto-detects diff scope across pull requests and review cycles, applying MVP mapping rules and fallback heuristics to generate a report of candidate files.

Yes, it operates during docs steps across pull request review cycles. It analyzes git changes and surfaces impacted documentation files with reasons and confidence scores to guide reviewers without modifying the files.

The limitation is that it relies on simple conventions and fallback heuristics rather than semantic understanding. It surfaces candidate files and confidence scores for reviewer guidance without editing, and may fall back to manual inspection if diff auto-detection fails.