c-review

Orchestrates parallel subagent security reviews of C/C++ codebases for memory corruption and race conditions.

Updated May 17, 2026
One-click install
npx skills add https://github.com/irrit-us/agent_misc --skill c-review-irrit-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: c-review
Source: https://github.com/irrit-us/agent_misc/tree/main/skills/c-review
Command: npx skills add https://github.com/irrit-us/agent_misc --skill c-review-irrit-us

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Auditing large native C/C++ codebases for memory safety bugs, integer overflows, and race conditions is slow and error-prone when done manually, and single-pass reviews miss entire bug classes. This Skill coordinates a multi-worker, multi-judge pipeline that systematically covers dozens of vulnerability classes and produces deduplicated, severity-rated findings. ## Core Features & Use Cases - Parallel cluster-based review: Spawns multiple worker subagents, each assigned a cluster of bug classes (buffer overflows, use-after-free, integer overflows, races, format strings) selected deterministically from a manifest based on codebase flags (C++, POSIX, Windows) and threat model. - Two-stage judge pipeline: A dedup judge merges duplicate findings by exact location, then an FP/severity judge assigns verdicts (TRUE_POSITIVE through OUT_OF_SCOPE) and threat-model-aware severity ratings. - Machine-readable output: Produces per-finding markdown files with YAML frontmatter, a human-readable REPORT.md, and a SARIF 2.1.0 export for integration with code scanning tools. - Use Case: Point it at a network-facing C daemon, choose a REMOTE threat model and high severity filter, and receive a deduplicated report of remotely exploitable memory corruption bugs with reachability traces and fix recommendations. ## Quick Start Run a security review of this C++ codebase with a remote attacker threat model and report only high severity findings.

Frequently Asked Questions about c-review

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

FAQPage Schema
How do I run a C/C++ security review with this skill?▼

Invoke the skill and provide a threat model (REMOTE, LOCAL_UNPRIVILEGED, or BOTH), a worker model, and a severity filter. It then probes the codebase, builds a run plan, spawns parallel review workers, and returns a deduplicated REPORT.md with findings.

What vulnerability types does a C/C++ security audit cover?▼

The review covers 47 always-on bug classes including buffer overflows, use-after-free, integer overflows, race conditions, format strings, and unsafe stdlib usage, expanding to up to 64 classes when C++ or Windows conditional clusters are enabled.

Can I scope the review to a subdirectory of my repo?▼

Yes, you can pass a scope subpath so findings are only filed inside that subtree. Workers may still read the broader repository as read-only context to verify callers, build flags, and reachability.

Does this skill work for kernel drivers or Rust code?▼

No. It explicitly excludes kernel drivers and modules on Linux, Windows, and macOS, managed languages like Java, C#, Go, and Rust, and embedded bare-metal code without libc. It targets userspace native C/C++ only.

What output formats does the security review produce?▼

Each run produces per-finding markdown files with YAML frontmatter, a dedup summary, an FP-judge summary, a human-readable REPORT.md filtered by severity, and a SARIF 2.1.0 file for code scanning tool integration.

Why does the review spawn a cache primer worker first?▼

The primer warms the shared prompt prefix so the parallel worker batch hits the prompt cache instead of each paying full cache-creation cost. Workers must be spawned foreground in one message; background spawns defeat the cache and waste roughly 15K tokens per worker.