Skip to content
Security
Skill

/sast-review

Run or ingest static application security testing (SAST) results on a codebase, triage them to remove false positives, and confirm the real issues with code evidence and remediation. Use when reviewing source code for security flaws or cleaning up noisy scanner output.

From plugin
awesome-claude-security
7111 skills17 agents13 commands1 MCP
Install
$ npx -y skills add jassics/awesome-claude-security --skill sast-review --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/sast-review

Context preview

The summary Claude sees to decide when to auto-load this skill.

Run or ingest static application security testing (SAST) results on a codebase, triage them to remove false positives, and confirm the real issues with code evidence and remediation. Use when reviewing source code for security flaws or cleaning up noisy scanner output.

SKILL.md

sast-review.SKILL.md
name: sast-review
description: >-
  Run or ingest static application security testing (SAST) results on a codebase,
  triage them to remove false positives, and confirm the real issues with code
  evidence and remediation. Use when reviewing source code for security flaws or
  cleaning up noisy scanner output.

Goal

A triaged SAST finding set: confirmed, code-evidenced issues mapped to CWE and ranked — with the false positives filtered out.

Steps

1. **Scope & scan** — identify languages/frameworks; run an appropriate SAST tool (e.g. Semgrep/CodeQL or the project's configured scanner), or ingest existing results. Note coverage and any excluded paths. 2. **Triage each finding** — open the flagged code and trace data flow from source (untrusted input) to sink. Classify: true positive / false positive / needs runtime confirmation. Watch for sanitizers/validation the tool missed. 3. **Confirm impact** — for true positives, identify the vulnerability class (CWE), reachability, and exploitability; mark which need dynamic confirmation (`web-app-security` / `api-security`). 4. **Score & rank** — severity (`security-reporting:cvss`) weighted by reachability; prioritize reachable, high-impact issues. 5. **Remediate** — give the specific code-level fix (parameterize, encode, validate, safe API) — and a secure pattern to prevent recurrence.

Output

A triaged findings table: id · CWE · file:line · class · reachability · TP/FP · severity · remediation. Confirmed issues → `security-reporting:finding`.

Notes

SAST is high-recall, low-precision — the value you add is triage. Always trace source→sink before accepting a finding, and flag what needs dynamic confirmation rather than over-claiming. Tune rules to cut recurring false positives. For Python or React/JS specifically, `secure-coding:safe-function-lint` covers a smaller, curated banned-function rule pack (CWE/ASVS-cited) *and* can enforce it via installed git hooks — this skill stays the broader, multi-language, scan-any- codebase pass; the two aren't mutually exclusive.

Read more
Ships withawesome-claude-security

A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.

Get the whole plugin

Other skills on awesome-claude-security.