docs-guard

Extract every claim from the docs — functions, flags, endpoints, config keys, versions — and verify each against its source of truth: the definition site, argument parser, route table, or changelog. This Skill provides a structured verification procedure and review checklist for exactly that pass.

Check that imports resolve, API signatures match the real definitions, samples run on a clean machine without hardcoded paths or credentials, and shown output matches actual output. The Skill's code-samples reference defines a full shippability checklist including error-path coverage.

Yes, it audits in-code documentation for paraphrased signatures, @param name and type drift, incorrect @throws lists, and wrong @since versions. It treats wrong docstrings that feed generated reference sites with the same severity as wrong READMEs.

Do not use it for production code review, test review, marketing copy, prose style editing, or documentation site theming. It verifies what docs claim about code, not the code itself, and does not enforce tone or style guides.

Models document from memory of how APIs usually look rather than reading the code in front of them, producing valid-looking but hallucinated invocations especially for infrequent APIs. Verification against the actual source is the only reliable detection method.