Scan code changes for security
Examine a pull request or a local diff for regressions in security.
Point the ZeroTwo Security plugin at a Git-backed set of changes. It checks which suspected security regressions are real and returns a report grounded in evidence, ready before you merge.
Best for
- Pull requests touching auth, parsing, file access, or secrets.
- Pre-merge checks of release branches or local patches.
Skills & Plugins
- Security: Security Diff ScanChecks a pull request, a commit, a branch diff, or a patch in your working tree, backed by attack-path evidence (
$security-diff-scan).
Starter prompt
Review the change instead of the whole repository
Use this when a change touches sensitive code: discovery and validation stay on the diff and its direct support. It supplements ordinary review.
Run a focused pass
-
Select
Check out or describe the exact change set.
-
Prompt
Enable the Security plugin from Customize, open a Work or Code task on the repository, then name the target and risky surfaces.
-
Stay read-only
Skip fix requests.
-
Check evidence
Read affected lines, validation results, and proof gaps.
Follow through on a finding
The Markdown and HTML reports list each finding with severity, confidence, affected lines, validation (including remaining uncertainty), and reachability. For actionable ones, start a separate task that invokes $fix-finding and cites the finding's title and affected lines, as in Fix a finding from your security scan.

