fact-check

Category: Tools & Productivity | Uploader: mbd-s | Downloads: 0 | Version: v1.0（Latest）

Spawns an auditor sub-agent to verify every factual claim in an incident report against evidence in the repo. Use after drafting or substantially editing a report.

Changelog: Source: GitHub https://github.com/mbd-s/dotfiles

Directory Structure

Current level: tree/main/claude/.claude/skills/fact-check/

📄 SKILL.md 2.1 KB

SKILL.md

---
name: fact-check
description: "Spawns an auditor sub-agent to verify every factual claim in an incident report against evidence in the repo. Use after drafting or substantially editing a report."
---

# Fact-Check Audit

## Usage

/fact-check <path_to_report>

## Instructions

1. Read the provided report and the relevant source files (logs, CLI output, terraform state, etc.).
2. Use the `Agent` tool to spawn a "Verification Agent."
3. The Verification Agent's ONLY job is to:
   - Identify every factual claim in the report.
   - Cross-reference it against evidence available in the repo (pasted logs, CLI output, config files). Only query live systems (AWS CLI, etc.) if the tools are available in the current session.
   - Normalize all timestamps to Berlin time (CET/CEST) and flag any source that uses a different timezone.
   - Classify each claim:
     - **PASS** — verified, with source cited (file path + line or command output)
     - **FAIL (critical)** — wrong root cause, incorrect metric, or misleading conclusion
     - **FAIL (minor)** — wrong timestamp, typo in resource name, or cosmetic inaccuracy
4. After the sub-agent finishes, **present the findings to the user** — do NOT edit the report automatically. List proposed fixes and wait for approval before making changes (per the plan-confirm-execute workflow).
5. Once approved, update the report:
   - Fix confirmed FAIL items or mark them as **[UNVERIFIED]**.
   - Append a Verification Log at the bottom of the document in this format:

```markdown
## Verification Log

| #   | Claim                             | Verdict         | Source                  | Notes                                            |
| --- | --------------------------------- | --------------- | ----------------------- | ------------------------------------------------ |
| 1   | DB CPU peaked at 97% at 14:32 CET | PASS            | cloudwatch-output.md:42 |                                                  |
| 2   | Deployment triggered the spike    | FAIL (critical) | —                       | No deploy found in timeline; marked [UNVERIFIED] |
```

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

fact-check

Directory Structure

SKILL.md

Report

Notice