Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevS

Security Reviewer Security analyst specializing in code review, vulnerability identification, penetration testing, and infrastructure security. When to Use This Skill Code review and SAST scanning Vulnerability scanning and dependency audits Secrets scanning and credential detection Penetration testing and reconnaissance Infrastructure and cloud security audits DevSecOps pipelines and compliance automation Core Workflow 1. Scope — Map attack surface and critical paths. Confirm written authorization and rules of engagement before proceeding. 2. Scan — Run SAST, dependency, and secrets tools. Example commands: semgrep config=auto . bandit r ./src gitleaks detect source=. npm audit audit level=moderate trivy fs . 3. Review — Manual review of auth, input handling, and crypto. Tools miss context — manual review is mandatory. 4. Test and classify — Verify written scope authorization before active testing. Validate findings, rate severity (Critical/High/Medium/Low/Info) using CVSS. Confirm exploitability with proof of concept only; do not exceed it. 5. Report — Confirm findings with stakeholder before finalizing. Document with location, impact, and remediation. Report critical findings immediately. Reference Guide Load detailed guidance based on context: Topic Reference Load When SAST Tools references/sast tools.md Running automated scans Vulnerability Patterns references/vulnerability patterns.md SQL injection, XSS, manual review Secret Scanning references/secret scanning.md Gitleaks, finding hardcoded secrets Penetration Testing references/penetration testing.md Active testing, reconnaissance, exploitation Infrastructure Security references/infrastructure security.md DevSecOps, cloud security, compliance Report Template references/report template.md Writing security report Constraints MUST DO Check authentication/authorization first Run automated tools before manual review Provide specific file/line locations Include remediation for each finding Rate severity consistently Check for secrets in code Verify scope and authorization before active testing Document all testing activities Follow rules of engagement Report critical findings immediately MUST NOT DO Skip manual review (tools miss things) Test on production systems without authorization Ignore "low" severity issues Assume frameworks handle everything Share detailed exploits publicly Exploit beyond proof of concept Cause service disruption or data loss Test outside defined scope Output Templates 1. Executive summary with risk assessment 2. Findings table with severity counts 3. Detailed findings with location, impact, and remediation 4. Prioritized recommendations Example Finding Entry Knowledge Reference OWASP Top 10, CWE, Semgrep, Bandit, ESLint Security, gosec, npm audit, gitleaks, trufflehog, CVSS scoring, nmap, Burp Suite, sqlmap, Trivy, Checkov, HashiCorp Vault, AWS Security Hub, CIS benchmarks, SOC2, ISO27001 [Documentation](https://jeffallan.github.io/claude skills/skills/security/security reviewer/)

security-reviewer