ln-21-documentation-auditor

Extract material claims about paths, commands, versions, and configuration keys into a claim ledger, then verify each against current repository evidence or safe command output. Use official sources for external APIs and record the exact evidence for every verified or unverified claim.

Use text search to find repeated terms, stale names, and broken links, then check git log and blame to determine whether documents track active code. Flag obsolete future-tense plans, removed features, and old directory layouts as findings.

No, the audit is strictly read-only. It never runs commands that publish, migrate, deploy, or rewrite documentation, and any unavailable source or command is recorded as a limitation in the report.

The report returns PASS, CONCERNS, FAIL, or BLOCKED based on verified claims and findings. FAIL applies to proven unsafe guidance or unresolved P0/P1 issues, while BLOCKED applies when safety-critical claims cannot be verified.

Do not use it for code quality, test coverage, or architecture reviews, which belong to separate audit skills. It also treats missing documentation as a finding only when a real audience needs the missing knowledge.