chain-of-verification

Verify factual claims about code against source files and dependencies.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill chain-of-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chain-of-verification
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/chain-of-verification
Command: npx skills add https://github.com/cropsgg/skills --skill chain-of-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces verification of every factual claim against the actual codebase, ensuring outputs are grounded in source data and reducing hallucinations.

Core Features & Use Cases

  • Verification chains for code, dependencies, and API contracts to ensure accuracy.
  • Fast, deterministic checks using simple source queries like grep, read_file, and glob.
  • Use cases include documentation generation, code explanations, and policy statements that must be provably true.

Quick Start

Run the verification chain on every factual claim and correct discrepancies using the actual source data.

Frequently Asked Questions about chain-of-verification

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

FAQPage Schema
How do I verify factual claims against my source code to prevent hallucinations?

To verify factual claims against source code, automate verification chains using deterministic checks like grep, read_file, and glob. This grounds outputs in actual source data to reduce hallucinations.

What is codebase verification for documentation generation?

Codebase verification for documentation generation is the process of checking explanations about code behavior, API contracts, and dependency versions against actual source files. It ensures documentation is provably true and grounded in source data.

Can I audit API contracts and dependency versions using deterministic checks?

Yes, you can audit API contracts and dependency versions using fast, deterministic checks. Applying source queries like grep, read_file, and glob across development artifacts verifies dependency claims accurately.

How do I check file existence and code behavior claims across development artifacts?

You check file existence and code behavior claims by running automated verification chains across development artifacts. This applies deterministic source queries to validate that statements match the actual codebase.

What are the limitations of using grep and glob for source code verification?

The limitations of using grep and glob for source code verification relate to their deterministic nature; while fast for simple source queries, complex or dynamic behavioral claims may require broader verification chains to ensure accuracy.