Audit the repository's docs/ content against the current codebase, find missing, incorrect, or stale documentation, and refresh the affected pages. Use when the user asks to review docs coverage, find outdated docs, compare docs with the current repo, or fix documentation drift across features, settings, tools, or integrations.
Audit docs/ from the repository outward: inspect the current implementation, identify documentation gaps or inaccuracies, and update the relevant pages. Keep the work inside docs/ and treat code, tests, and current configuration surfaces as the authoritative source.
Read references/audit-checklist.md before a broad audit so the scan stays focused on high-signal areas.
Inspect the repository areas that define user-facing or developer-facing behavior.
docs/Look for three classes of issues:
Prefer proving a gap with repository evidence before editing. Use current code and tests instead of intuition.
Fix the highest-cost issues first:
Update the smallest correct set of pages under docs/.
_meta.ts when adding or moving pagesBefore finishing:
docs/ for old terminology and replaced config keys_meta.tsdocs/.Produce a focused docs refresh that makes the current repository more accurate and complete. Summarize the audited surfaces and the concrete pages updated.