ln-614-docs-fact-checker

Extract verifiable claims from Markdown docs and validate them against the codebase.

Updated Mar 14, 2026

Search Tags:#documentation #markdown #consistency #codebase #audit #fact-check

Ready to run

npx skills add https://github.com/0xtaoist/taogate --skill ln-614-docs-fact-checker-0xtaoist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-614-docs-fact-checker
Source: https://github.com/0xtaoist/taogate/tree/main/ln-614-docs-fact-checker
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-614-docs-fact-checker-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often contains verifiable facts that are hard to audit across large repos. This Skill automates extraction of claims from Markdown files and validation against the codebase to prevent contradictions and drift.

Core Features & Use Cases

Extracts verifiable claims from all Markdown documentation, including paths, versions, counts, configurations, and endpoints.
Validates each claim against the actual source code and project manifests.
Detects cross-document contradictions to maintain consistent and trustworthy documentation.

Quick Start

Run the docs-fact-checker to scan all Markdown files in the repository and generate a verified audit report.

Frequently Asked Questions about ln-614-docs-fact-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify documentation claims against my codebase?▼

To verify documentation claims against your codebase, this Skill extracts verifiable facts from Markdown files and validates each item against the actual source code and project manifests to prevent contradictions and drift.

What is cross-document contradiction detection in Markdown?▼

Cross-document contradiction detection scans all Markdown documentation to ensure consistent facts across the repository. It identifies conflicting claims, such as mismatched paths or version numbers, to maintain trustworthy documentation.

How do I audit Markdown files for paths, versions, and endpoints?▼

Auditing Markdown files for paths, versions, and endpoints is done by scanning all documentation to extract these verifiable claims. The Skill then checks each extracted configuration against the actual codebase and manifests.

Can I detect documentation drift in large repositories?▼

You can detect documentation drift in large repositories by running an automated audit that extracts claims from all Markdown files and validates them against the source code to prevent inconsistencies over time.

How do I generate a verified audit report for Markdown documentation?▼

To generate a verified audit report for Markdown documentation, run the docs-fact-checker to scan all Markdown files in the repository, validate the extracted claims against the codebase, and output the results.

Does the fact-checker work without external dependencies?▼

The fact-checker works without external dependencies, requiring no additional components to scan Markdown files, extract verifiable claims, and validate them against the codebase to generate an audit report.