doc-maintenance

Detect documentation drift by comparing top-level repository docs against recent git history. The audit identifies shipped features missing from README or SPEC files and flags inconsistencies, ensuring documentation accuracy without manual review.

Yes, you can automate documentation updates by creating a maintenance branch and opening a draft PR. This workflow proposes minimal edits to fix drift detected in repository docs, streamlining the review process for documentation changes.

The best way to audit top-level docs for accuracy is to scan repository history for recent feature merges and compare them against existing documentation. This automated drift detection ensures documentation matches the actual codebase state.

No, the documentation audit applies strict rules to avoid changes to non-documentation files. It only proposes minimal edits to top-level documentation files like README and SPEC, ensuring source code remains untouched during the maintenance process.

You need to run a documentation drift audit after major feature merges, when asked to review docs for accuracy, or on a periodic schedule. This ensures your top-level repository documentation stays synchronized with the actual codebase.