review-docs

To check for documentation drift, run a diff-driven audit against origin/main to identify outdated examples and missing docs. This produces a concise report listing impacted files, inconsistencies, and recommended updates.

A documentation audit scavenge targets AGENTS.md, README.md, docs/, SPEC.md, CHANGELOG.md, and CONTRIBUTING.md. It scans these locations to find missing or inconsistent documentation introduced by code changes.

Yes, you can audit documentation using explicit files and directories instead of a diff. This allows you to manually scope the review to specific project areas to find missing or inconsistent docs.

The best way to keep docs in sync with code is running diff-driven audits tied to code changes. This identifies documentation drift and produces actionable reports with recommended updates for impacted files.

A documentation drift report includes impacted files, missing or inconsistent docs, and recommended updates. It provides a concise, high-density summary of gaps found during the scope audit.