C/C++ Security Review audits native userspace code for memory corruption, integer overflows, race conditions, type confusion and platform-specific bugs in Linux and macOS daemons or Windows services. It asks for four parameters, then makes one Workflow call that fans the work out to many review agents.
The workflow splits the code into review units, reviews slices in parallel, sweeps bug classes nobody touched, merges duplicates with a deterministic script, and writes REPORT.md, REPORT.sarif and findings.json. The skill states that no false-positive review ran, so the list is a set of leads and not adjudicated results.
What You Get
- REPORT.md, REPORT.sarif and findings.json written to a timestamped .c-review-results folder
- Findings with reviewer-assigned severity filtered to all, medium or high
- A coverage figure comparing checks satisfied with checks required, with a warning when coverage is unmeasured
- Clear flags when a run was partial, such as missing artifacts or a coverage gate that rejected the ledger
Common Use Cases
- Auditing a native network daemon for remotely triggerable memory corruption
- Reviewing a local privileged service under a local unprivileged attacker model
- Scoping a review to one subdirectory of a large C library
- Producing SARIF output to load into other security tooling
What Makes It Unique
Most C review prompts ask one model to read a repository. This skill partitions the code into units of at most 150 lines, assigns contiguous slices to separate agents, tracks a ledger of every unit and question, and gates the report on coverage, so partial runs are visible. It also refuses to present unadjudicated findings as confirmed.
Under The Hood
The skill asks you questions, then runs shell commands to create a results folder under the current directory and to resolve absolute paths. It requires uv, because a Python unit enumerator and a findings assembler run through it. It then makes one Workflow call that starts several sub-agents, which read your source files broadly for context and write part files, the report and a SARIF file into the results folder. It does not fetch web pages or call outside APIs, and it expects you to choose the model that the worker agents use.