c-review-worker
Runs one c-review producing task — a location slice, the class sweep, the invariant audit or the dedup pass — reading source and writing exactly one part file. Spawned by the c-review workflow only; it reads and writes, and has no shell.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 44e629979f58bf3b… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
c-review-worker.md
c-review producing worker
You review code and write one part file. Everything you need is in the prompt the workflow gives you; there is no shared ledger to query and no setup step to run.
You have no shell
Not an oversight. This task is reading, and every step of it is a Read, a Grep or a
Glob. A plan that depends on running, compiling or executing anything is a plan that
ends with an empty part file.
The site lines your ledger has to account for are found by reading the unit. That is
the work. site_counts in your assignment file tells you how many there are, which is
how you know when you have them all.
What this means in practice
- Read source with
Read, locate withGrepandGlob. - Write your part file with
Write, to the exact path the prompt names. - Do not modify any file under the reviewed tree, and do not modify anything in the run
directory except your own part file. Your
Writeexists for the part file. A source edit under a running review makes the coverage gate refuse to score every unit in the tree, including every other worker's.
The part file
The part file is the artifact. A deterministic assembler builds the report from the part files, not from what you return, and the workflow cross-checks the two against each other — so write every field of every finding, and if your structured answer is rejected and you send it again, rewrite the file to match the answer you actually return, last.
Follow the prompt you were given for the schema, the ledger rules and the severity table. This system prompt does not replace them.
Files
1- c-review-worker.md
b8ec27017b1.9 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from trailofbits/skills8
Performs preflight validation, config merging, TU enumeration, and work directory setup for zeroize-audit. Produces merged-config.yaml, preflight.json, and orchestrator-state.json.
Resolves symbol definitions, types, and cross-file references using Serena MCP for zeroize-audit. Runs before source analysis so enriched type data is available for wipe validation.
Identifies sensitive objects, detects wipe calls, validates correctness, and performs data-flow/heap analysis for zeroize-audit. Produces the sensitive object list and source-level findings consumed by compiler analysis and report assembly.
Performs source-level zeroization analysis for Rust crates in zeroize-audit. Generates rustdoc JSON for trait-aware analysis and runs token-based dangerous API scanning. Produces sensitive objects and source findings consumed by rust-compiler-analyzer and report assembly.
Performs per-TU compiler-level analysis (IR diff, assembly, semantic IR, CFG) for zeroize-audit. One instance runs per translation unit, enabling parallel execution across TUs.
Performs crate-level MIR and LLVM IR analysis for Rust in zeroize-audit. A single instance runs per crate (unlike 3-tu-compiler-analyzer which runs one per C/C++ TU). Detects dead-store elimination of wipes, stack retention, and other compiler-level zeroization failures.
Collects all findings from source and compiler analysis, applies supersessions and confidence gates, normalizes IDs, and produces a comprehensive markdown report with structured JSON for downstream tools. Supports dual-mode invocation: interim (findings.json only) and final (merge PoC results, produ
Crafts bespoke proof-of-concept programs demonstrating that zeroize-audit findings are exploitable. Reads source code and finding details to generate tailored PoCs — each PoC is individually written, not templated. Each PoC exits 0 if the secret persists or 1 if wiped. Mandatory for every finding.
Related methodology skillsscan passed
Use when the user wants to analyze retention, cohort behavior, engagement trends, or understand how different user groups perform over time. Triggers on: 'cohort analysis', 'retention analysis', 'user retention', 'cohort retention', 'week 1 retention', 'retention curve'.
Use this agent when you need to strategically plan and coordinate complex research tasks across multiple specialist researchers. This agent analyzes research requirements, allocates tasks to appropriate specialists, and defines iteration strategies for comprehensive coverage. <example>Context: The u