fact-checker

Fact-checking validates modifications against originals to ensure no critical facts, behaviors, or context are lost. It performs element-by-element comparison and generates detailed discrepancy reports with file and line references, letting you confirm refactors, rewrites, and edits maintain factual integrity without altering files.

Yes. Fact-checking applies to any content type—code, documentation, or text—where modifications must preserve factual accuracy and completeness. It validates imports, rewrites, and edits across formats using systematic diff analysis.

Reports detail severity and impact analysis for each discrepancy, with specific file and line references. This actionable, structured output identifies where factual gaps or behavioral changes occur, enabling informed review without implementation recommendations.

No. Fact-checking performs pure validation without modifying files. It analyzes original versus modified content, reports findings, and leaves all files unchanged so you retain full control over changes.

Use fact-checking when intent preservation, context retention, and element-by-element accuracy matter—such as code refactors where logic must stay identical, documentation rewrites where facts must remain intact, or imports where all critical behaviors must transfer unchanged.

Fact-checking provides systematic, structured validation focused on factual accuracy and context preservation with detailed discrepancy reports. Standard review is broader; fact-checking fills the specific need for rigorous, comparable verification that critical facts survived modification.