doc-maintenance

Documentation drift is detected by comparing top-level docs like README.md and doc/SPEC.md against recent git history. This identifies missing or outdated content after feature merges, proposing minimal factual edits as PR-ready changes.

Yes, you can automatically fix outdated documentation by creating a branch and opening a PR. This workflow builds a change summary from detected drift and proposes minimal, factual edits directly to the repository.

Auditing repository documentation for accuracy after a major merge involves comparing top-level docs against recent git history. This detects drift and proposes minimal, PR-ready edits to keep public docs aligned with shipped features.

You should run a documentation audit to prevent content drift after major feature merges or on a periodic review schedule. This ensures top-level documentation remains accurate and aligned with shipped features over time.

Yes, documentation drift detection works specifically with README.md, doc/SPEC.md, and doc/PRODUCT.md. It compares these top-level files against recent git history to identify missing or outdated content and propose minimal edits.