doc-maintenance

To detect documentation drift after a feature release, audit target documents like README.md and SPEC.md against recent git history. This process compares code changes to user-facing docs, identifies inconsistencies, and proposes minimal edits to fix inaccuracies.

Yes, you can automatically create a branch and open a PR to fix outdated docs. The maintenance audit identifies drift between your code and documentation, proposes the necessary minimal edits, and generates a pull request directly from the changes.

The best way to audit README and SPEC files for accuracy is comparing them against recent git commits. This surfaces drift between code modifications and user-facing documentation, allowing you to review and apply minimal corrective edits.

Perform a periodic documentation maintenance review by running an audit check on files such as README.md, doc/SPEC.md, and doc/PRODUCT.md. This compares current docs against recent git history to surface drift and open a PR with proposed fixes.

Documentation drift occurs when user-facing docs are not updated after code changes. Running a maintenance audit compares target documents against recent git history to identify these inconsistencies and propose minimal edits for correction.