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
11111 skills17 agents13 commands1 MCP

Claude Code

$ npx -y skills add jassics/awesome-claude-security --skill sast-review --agent claude-code

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
@jassics
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.

11111 skills17 agents1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
11
Star history of jassics/awesome-claude-security on GitHub, a chart by star-history.com

Other skills on awesome-claude-security.

More skills from other plugins.

api-security

api-security

Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication,…

@zhaoxuya520@zhaoxuya520Install Skill
nemoclaw-user-guide

nemoclaw-user-guide

Find official NemoClaw documentation for installation, configuration, operation, or troubleshooting. Also handles requested docs…

nemoclaw12d23k
@nvidia@nvidiaInstall Skill

Questions about sast-review.

Which coding agents can use sast-review?
sast-review installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.