Fact-check repository documentation against code, configuration, and command outputs.
npx skills add https://github.com/nicograef/handbook --skill verify-docs-nicograef
Please help me install this Agent Skill. Skill: verify-docs Source: https://github.com/nicograef/handbook/tree/main/.claude/skills/verify-docs Command: npx skills add https://github.com/nicograef/handbook --skill verify-docs-nicograef
This Skill solves the problem of documentation rot, where technical guides, runbooks, and READMEs drift away from the actual state of the code, configuration, and infrastructure they describe.
Run the verify-docs skill to audit the entire repository documentation for accuracy against the current codebase.
High-intent search queries and answers about installing and using this skill.
Documentation verification is performed by fact-checking repository docs against ground truth sources like code, config files, and command outputs to identify false claims, stale information, and broken references.
A consistency audit detects stale information and contradictions between documents by validating claims against evidence-based ground truth sources rather than relying on memory, ensuring docs match the implementation.
Checking for broken references involves auditing the committed corpus to identify dead internal and external links, ensuring technical guides and runbooks remain synchronized with the current infrastructure.
Yes, automated documentation auditing is ideal after a major refactor to ensure setup guides and command examples still match the updated repository structure and configuration keys.
Evidence-based verification works by validating documentation claims against read-only command outputs and configuration files to detect drift, ensuring technical writing remains synchronized with the technical implementation.
Ikram-AlamEvaluate agent outputs against rubrics and ground truth with multi-dimensional scoring.
basmawebinfo-hubVerify technical documentation claims against source code evidence.
Asharf30Cross-reference documentation claims against source code implementations.
riddopicApply documentation style principles for voice, tone, structure, and LLM-friendly patterns.
