fact-checking

Identify and triage verifiable claims in code and documentation with evidence.

8|5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill fact-checking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fact-checking
Source: https://github.com/axiomantic/spellbook/tree/main/skills/fact-checking
Command: npx skills add https://github.com/axiomantic/spellbook --skill fact-checking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill helps teams ensure accuracy and reliability of code changes and documentation by systematically triaging claims, gathering evidence, and producing clear verdicts.

Core Features & Use Cases

  • Claim triage: Identify, categorize, and prioritize verifiable claims found in code comments, docs, and commit messages.
  • Evidence-backed verdicts: Require traceable evidence for each conclusion and generate bibliographies.
  • Automation-ready outputs: Produce structured findings and an implementation plan when fixes are needed.
  • Use Case: A codebase audit where multiple contributors propose changes; run this Skill to validate each claim before merge.

Quick Start

Run a targeted scan on the given codebase to extract, verify, and report on verified claims.

Frequently Asked Questions about fact-checking

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

FAQPage Schema
How do I verify technical claims in code comments and documentation?

To verify technical claims in code and documentation, you can systematically triage statements, gather traceable evidence, and produce structured verdicts. This ensures accuracy by validating comments and docs against the actual codebase.

Can I run evidence-driven verification on uncommitted branch changes?

Yes, evidence-driven verification can apply to specified scopes including branch changes, uncommitted changes, or the full repository. It identifies verifiable claims within those boundaries and reports findings against them.

What is the best way to audit codebase claims before a merge?

The best way to audit codebase claims before a merge is to extract and categorize verifiable statements from commit messages and docs, then require traceable evidence for each conclusion to ensure reliability.

Does fact-checking documentation automatically generate an implementation plan?

Yes, fact-checking documentation automatically generates an implementation plan when fixes are needed. It produces automation-ready structured findings and a bibliography to guide necessary corrections.

How do I triage verifiable claims found in commit messages?

To triage verifiable claims found in commit messages, identify, categorize, and prioritize them. Generate clear verdicts by matching each claim against traceable evidence within the codebase.