ln-614-docs-fact-checker

Name: ln-614-docs-fact-checker
Availability: InStock
Author: dorrio

Extract claims from Markdown files and verify them against the codebase.

Updated Dec 11, 2025

Search Tags:#documentation #markdown #consistency #fact-checking #code verification #claims

Ready to run

npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-614-docs-fact-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-614-docs-fact-checker
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-614-docs-fact-checker
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-614-docs-fact-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ensuring consistency and accuracy across documentation and the codebase by automatically verifying claims made in Markdown files against the actual code.

Core Features & Use Cases

Claim Extraction: Identifies verifiable statements (paths, versions, counts, configs, names, endpoints) within all .md files.
Codebase Verification: Cross-references extracted claims with the codebase to confirm their accuracy.
Contradiction Detection: Identifies discrepancies between different documentation files or between documentation and code.
Use Case: Before releasing a new version, use this Skill to ensure that all version numbers, API endpoints, and configuration parameters mentioned in the README and other documentation files accurately reflect the deployed code.

Quick Start

Use the ln-614-docs-fact-checker skill to verify all claims in the codebase's markdown files.

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 accuracy against my codebase?▼

Documentation consistency checking works by extracting verifiable claims such as paths, versions, counts, configurations, names, and endpoints from Markdown files, then validating each claim directly against the source code.

How do I check for contradictions between different Markdown documents?▼

Contradiction detection between Markdown files is performed by cross-checking all extracted claims across documents to identify discrepancies in paths, versions, counts, configurations, names, and endpoints.

Can I use this to verify API endpoints mentioned in my README?▼

Yes, API endpoints mentioned in Markdown files are targeted by extracting endpoint claims and verifying them directly against the codebase to ensure code-documentation alignment.

Does this fact-checker work with all Markdown files in my repository?▼

Yes, this fact-checking process works with all Markdown files in a repository by extracting and verifying claims from every `.md` file to ensure complete code-documentation alignment.

What specific types of claims can be verified in documentation?▼

Verifiable claims extracted from Markdown files include paths, versions, counts, configurations, names, and endpoints, all of which are cross-referenced with the codebase for accuracy.

When should I run documentation consistency checks before a release?▼

You should run documentation consistency checks before a new release to ensure all version numbers, API endpoints, and configuration parameters in Markdown files accurately reflect the deployed codebase.