Individual skill

c-security-review

Use when the user requests a userspace C or C++ security review with a threat model and severity filter and wants validated findings. Not for kernel or bare-metal code: use kernel-security.

.devin/skills/c-security-review/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# C security review

## Contract

| Field | Bound contract |
|---|---|
| Trigger | The user requests a complete userspace C or C++ security review with an explicit threat model, severity filter, and model. |
| Authority | Reversible local: write only the `.c-review-results/<stamp>/` run directory under the current working directory. Roll back by deleting that directory. No remote mutation. |
| Side effect | A `.c-review-results/<iso-timestamp>/` directory holding `units.json`, `ledger.json`, `findings.json`, `REPORT.md`, and `REPORT.sarif`. The reviewed tree is never modified. |
| Done | Every unit in scope has a ledger row per question or is named as uncovered, every reported finding carries a validation verdict of `confirmed` or `needs-context`, refuted findings are removed with their count disclosed, and REPORT.md and REPORT.sarif agree. |

## Inputs

Required, resolved before review. Infer from free text on the invocation ("remote" to `REMOTE`, "local" to `LOCAL_UNPRIVILEGED`, "all" or "high only" to the filter, an explicit model name, "X only" to `scope_subpath`), then ask once for whatever stays unresolved. Never silently default a required parameter.