doc-maintenance

To audit documentation drift, compare top-level docs like README and SPEC against recent git commits to identify missing or outdated features, then apply minimal edits to correct the discrepancies and open a PR.

The best way to keep README and SPEC files synchronized is to run periodic audits that classify recent commits into Feature, Breaking, or Structural changes, generate a concise summary, and patch the docs with minimal edits via a PR.

Yes, you can automatically generate pull requests to fix outdated documentation by creating a branch, applying minimal drift-correcting edits to target files, and opening a PR with a standardized body referencing an audit checklist.

Documentation drift detection works for both periodic reviews and major feature merges by detecting changes since the last review, classifying them, and proposing minimal edits to update top-level documents such as README, SPEC, and PRODUCT files.

Classify recent commits into Feature, Breaking, or Structural categories to build a concise change summary, then use that classification to apply minimal targeted edits to top-level project documentation files.

Run a documentation audit when asked to review docs for accuracy, immediately after major feature merges, or on a periodic schedule to ensure top-level documents reflect the current state of shipped features in git history.