fact-check

Audits Rust and other code for logic errors, unsafe casts, and problematic patterns.

25|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/srid/agency --skill fact-check-srid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fact-check
Source: https://github.com/srid/agency/tree/main/.apm/skills/fact-check
Command: npx skills add https://github.com/srid/agency --skill fact-check-srid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit code for correctness and rigor, focusing on logic errors, silent error swallowing, and unjustified fallbacks to prevent brittle software.

Core Features & Use Cases

  • Targeted correctness audits: identify and report logic flaws, silent failures, and unsafe fallbacks across changed code or entire codebase.
  • Diff-aware analysis: analyze diffs between branches (e.g., main...HEAD) or entire repo to surface issues in context.
  • Use Case: imagine reviewing a PR with subtle failure modes; this skill highlights root causes and suggests fixes to harden commits.

Quick Start

Run a targeted audit on the current branch to catch logic flaws before merging.

Frequently Asked Questions about fact-check

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

FAQPage Schema
How do I audit code for logic errors and silent error swallowing?

A logic audit analyzes your codebase or branch diffs to identify logic errors, silent error swallowing, and unjustified fallbacks. It reads target files or diffs to surface these issues across changes and configurations, then reports findings with file and line context and proposes concrete fixes.

How do I catch hidden bugs in a pull request before merging?

To catch hidden bugs in a pull request before merging, perform a diff-aware analysis between branches like main and HEAD. This highlights subtle failure modes, identifies root causes within the changed code, and suggests specific fixes to harden your commits.

Can I run a static analysis audit on an entire codebase or just specific diffs?

You can run a static analysis audit on either an entire codebase or specific branch diffs. The audit applies to diffs in the current branch or the entire repository to surface correctness issues, silent failures, and unjustified fallbacks across changes and configurations.

What is the best way to find unjustified fallbacks and silent failures in code?

The best way to find unjustified fallbacks and silent failures in code is to run a rigorous logic audit. This process evaluates code correctness and rigor by reading your target files or diffs, reporting findings with file and line context, and proposing concrete fixes to prevent brittle software.

Does defensive coding logic audit work without external dependencies?

Yes, defensive coding logic audit works without external dependencies. It evaluates code correctness and rigor directly by reading target files or diffs to identify logic errors, silent error swallowing, and unjustified fallbacks, then proposes concrete fixes with file and line context.