docs-updater

You can update project documentation after implementing a feature by automatically analyzing code changes and git diffs to identify documentation impact. This process scans recent feature work to generate a concise plan for refreshing your project docs and surfacing gaps for human review.

You can update CLAUDE.md and README.md by applying a documentation review process that analyzes git diffs from merged features. This automatically assesses code changes and outputs accurate summaries, usage notes, and new references directly into your project documentation files.

The best way to review documentation impact after a code merge is to run an automated documentation maintenance process that evaluates feature changes. It uses issue data and git diffs to determine what needs updating, then outputs a concise plan for CLAUDE.md, README.md, and docs/.

Yes, this documentation review process works with codebases that contain CLAUDE.md, README.md, and a docs/ directory. It applies to your existing project structure to ensure documentation reflects recent work across features and epics without requiring a new setup.

You should run documentation updates for feature implementations immediately after a feature is merged. Running the process at this stage refreshes project docs by capturing the latest code changes and ensuring documentation accuracy before gaps can accumulate.

A limitation of automating documentation maintenance with git diffs is that it outputs a concise plan for human review rather than fully autonomous updates. It surfaces documentation gaps and generates summaries, but users must review the proposed changes for CLAUDE.md, README.md, and docs/.