docs-audit-and-refresh

A documentation gap analysis scans your docs/ tree against the current codebase and tests to map missing pages and detect drift. It identifies outdated references and prioritizes high-impact areas for a targeted content refresh.

Refreshing project docs to align with code involves reading current code, tests, and configuration, then comparing them against existing pages. This yields minimal, high-signal edits with validation steps to ensure accurate documentation coverage.

Detecting documentation drift in a codebase requires comparing the docs/ directory against the actual implementation surface. By inventorying existing coverage and highlighting where docs lag behind code, you isolate outdated references for necessary updates.

A docs audit requires a project with an existing docs tree and codebase surface areas. Without a docs/ directory to inventory, there is no baseline to compare against the code for gap detection or targeted refresh planning.

Validating updated documentation after a refresh involves running specific checks against the newly edited pages. The audit process outputs a focused set of edits alongside these validation steps to verify refreshed docs accurately reflect the codebase.