Command
Auto
/factcheck
Fact-check a file before publication
Overview
/factcheck is a standalone command for quick, targeted fact verification. Point it at any file — article, blog post, documentation, social media draft — and it extracts all verifiable claims, checks each against authoritative sources, and reports which claims are accurate, outdated, misleading, or unverifiable. Use it for a fast check outside the full editorial pipeline of /dr-edit.
Usage
/factcheck path/to/article.md
/factcheck blog/migration-post.md
/factcheck "Social Media/draft-post.md"What It Does
- Extract Claims — reads the file and identifies all statements that can be objectively verified: statistics, dates, version numbers, technical specifications, historical facts, attribution, and comparative claims.
- Verify Each Claim — searches authoritative sources (official documentation, peer-reviewed sources, reputable news) using web search and fetch. Critical claims are cross-referenced with 2+ independent sources.
- Assign Verdicts — each claim receives one of six verdicts:
- ACCURATE — confirmed by authoritative source(s)
- INACCURATE — contradicted by authoritative source(s)
- OUTDATED — was accurate but information has changed
- MISLEADING — technically true but presented in a way that creates false impression
- UNVERIFIABLE — no authoritative source found to confirm or deny
- NEEDS_CONTEXT — true only under specific conditions that should be stated
- Report — presents a summary with each claim, its verdict, and the source used for verification. Inaccurate claims include the correct information.
- Correct — after approval, applies corrections to the file.
Arguments
The file path to fact-check. Required.
Output
Fact-check report with claim-by-claim verdicts and sources. Corrected file (after approval).
Example Session
> /factcheck blog/postgres-migration.md
Extracting claims... 15 found
Checking:
"PostgreSQL 17 was released in September 2024"
→ ACCURATE (postgresql.org/about/news/2955)
"PostgreSQL is 3x faster than MySQL for analytical queries"
→ MISLEADING (depends on query type and configuration)
"UUID v7 was added in PostgreSQL 16"
→ INACCURATE (added in PostgreSQL 17)
Correction: "UUID v7 support was introduced in PostgreSQL 17"
Results: 12 ACCURATE, 1 MISLEADING, 1 INACCURATE, 1 NEEDS_CONTEXT
Apply corrections? (y/n)When to Use
- Quick check of a single article before publishing
- Verifying claims in documentation
- Reviewing a social media post draft
- When you need fact-checking without the full editorial pass of /dr-edit