← All use cases

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.

Intermediate
30m

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 Scan
    Checks 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

Use $security-diff-scan on the branch feature/upload-parser compared to main. I'm authorized to review this repository. Pay extra attention to file path handling, archive extraction, and anywhere secrets or auth tokens are read. Stay read-only, and give me a Markdown report listing each finding with its severity, confidence, affected lines, and evidence, and note anything you couldn't validate.

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

  1. Select

    Check out or describe the exact change set.

  2. Prompt

    Enable the Security plugin from Customize, open a Work or Code task on the repository, then name the target and risky surfaces.

  3. Stay read-only

    Skip fix requests.

  4. 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.

Related use cases