ze-review-docs

To check documentation accuracy against a codebase, generate a scope-specific inventory and run consistency checks for stale anchors, broken links, invalid examples, and terminology mismatches. The process compares documented features to current code and categorizes issues before fixes.

Documentation drift occurs when docs become inaccurate or incomplete relative to the codebase. You find stale content by building an inventory of paths and update dates, then validating anchors, internal links, examples, and terminology to report missing or incorrect features.

Validating broken links and anchors in technical documentation requires running mechanical checks against the chosen docs scope. This process identifies broken internal links and missing anchors, categorizing them as quality problems within a findings report for approval.

Yes, you can target a specific section of architecture or API docs. The review process applies to targeted areas such as guide, wire, config, or plugin docs to generate a focused inventory and run consistency checks on that scope.

The best way to audit terminology mismatches in project docs is to run a factual review against the current codebase. This verification process identifies terminology inconsistencies and categorizes them for approval before applying fixes.

No, the documentation review process does not apply fixes automatically. It generates a findings report categorizing issues as incorrect, stale, or incomplete, and requires explicit approval before any fixes are applied to the documentation.