---
name: Check Fact
slug: check-fact
category: Quality
description: "Check Fact verifies whether statements are accurate by checking a project's code, documentation, and config files. Use it to fact-check technical claims, architecture choices, or documentation accuracy."
github: "https://github.com/wasabeef/claude-code-cookbook/tree/main/plugins/en/skills/check-fact"
language: Shell
stars: 1131
forks: 111
install: "npx degit https://github.com/wasabeef/claude-code-cookbook/tree/main/plugins/en/skills/check-fact ~/.claude/skills/check-fact"
installs_to: ~/.claude/skills/check-fact
source_path: plugins/en/skills/check-fact/SKILL.md
collection_size: 25
category_size: 1354
collection_url: "https://dirskills.com/collections/wasabeef/claude-code-cookbook"
added: 2026-08-20T07:56:17.853Z
last_synced: 2026-08-20T07:56:17.853Z
canonical_url: "https://dirskills.com/skills/check-fact"
---

# Check Fact

Check Fact verifies whether statements are accurate by checking a project's code, documentation, and config files. Use it to fact-check technical claims, architecture choices, or documentation accuracy.

**Install:**

```bash
npx degit https://github.com/wasabeef/claude-code-cookbook/tree/main/plugins/en/skills/check-fact ~/.claude/skills/check-fact
```

## README

# Verify information accuracy against codebase and docs

Verifies if a statement is true by checking your project's code and documentation.

## Usage

```bash
# Basic usage
/check-fact "The Flutter app uses Riverpod"

# Check multiple facts at once
/check-fact "This project uses GraphQL and manages routing with auto_route"

# Check technical details
/check-fact "JWT is used for authentication, and Firebase Auth is not used"
```

## How It Works

1. **Where I Look (in order)**
   - The actual code (most trustworthy)
   - README.md and docs/ folder
   - Config files (package.json, pubspec.yaml, etc.)
   - Issues and PR discussions

2. **What You'll See**
   - `✅ Correct` - Statement matches the code exactly
   - `❌ Incorrect` - Statement is wrong
   - `⚠️ Partially correct` - Some parts are right, some aren't
   - `❓ Cannot determine` - Not enough info to check

3. **Proof I Provide**
   - File name and line number
   - Relevant code snippets
   - Matching documentation

## Report Format

```text
## Fact Check Results

### What You Asked
"[Your statement]"

### Verdict
[✅/❌/⚠️/❓] [True/False/Partial/Unknown]

### Evidence
- **File**: `path/to/file.dart:123`
- **Code**: [The actual code]
- **Note**: [Why this proves it]

### Details
[If wrong, here's what's actually true]
[If partial, here's what's missing]
[If unknown, here's what I'd need to check]
```

## Basic Examples

```bash
# Check the tech stack
/check-fact "This app is built with Flutter + Riverpod + GraphQL"

# Check if a feature exists
/check-fact "Dark mode is implemented and can be switched from user settings"

# Check architecture choices
/check-fact "All state management is done with Riverpod, BLoC is not used"

# Check security setup
/check-fact "Authentication tokens are encrypted and stored in secure storage"
```

## Collaboration with Claude

```bash
# Check dependencies
ls -la && find . -name "pubspec.yaml" -exec cat {} \;
/check-fact "The main dependencies used in this project are..."

# Check how something is built
grep -r "authentication" . --include="*.dart"
/check-fact "Authentication is custom built, not using third-party auth"

# Check if docs match reality
cat README.md
/check-fact "Everything in the README is actually implemented"
```

## When to Use This

- Writing specs: Make sure your descriptions are accurate
- Taking over a project: Check if you understand it correctly
- Client updates: Verify what's actually built
- Blog posts: Fact-check your technical content
- Presentations: Confirm project details before presenting

## Important

- Code beats docs: If they disagree, the code is right
- Old docs happen: Implementation is what matters
- No guessing: If I can't verify it, I'll say so
- Security matters: Extra careful with security-related facts