docs-review

A generic docs auditor: reads each markdown file in docs/, identifies what source code it documents (by scanning file paths, flag names, command syntax, state names, config examples), then cross-references those claims against actual source files. Reports drift (doc says X, code does Y) with file:line evidence.

When to Use

• Periodically (weekly cron) to catch docs that fall behind code changes
• Before a release to ensure docs are accurate against the current codebase
• After refactoring commands, config schemas, or state machines
• Skip if docs/ does not exist — exit cleanly with a note

When NOT to Use

• Pure narrative sections with no verifiable source claims (history, philosophy, rationale)
• Docs for external APIs you don't own — you can't grep their source
• Formatting or style reviews — only semantic drift matters

Invocation