← ClaudeAtlas

security-reviewlisted

Security audit against OWASP, SQL hardening, auth, secrets, dependencies, and LLM-specific threats. Use when the user says "security review", "security audit", or "security check". Also invoked from code-review's Pass B for security-sensitive stories.
rterakedis/leanwheel-skills · ★ 2 · Code & Development · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Security Review Skill **Goal:** Find exploitable vulnerabilities, data exposure, anti-patterns before production. All findings auto-scheduled. **Entry points:** `/security-review` (full or scoped, writes report) | Pass D (inline from code-review). --- ## Activation **`/security-review`:** Full or scoped? (Full: run all checklists; Scoped: run relevant categories only). **Pass D (inline):** Run categories from story's `Security Sensitivity:` field in Dev Notes. --- ## Security Sensitivity Flag Stories/specs must include `Security Sensitivity:` in Dev Notes if touching: auth, data-access, api, secrets, llm, payments, file-upload. Categories auto-set by `/create-story`. Pass D triggered by flag in `/dev-story`. --- ## Checklists Run applicable categories. For each item, mark: **Pass**, **Fail** (with file:line citation), or **N/A**. ### Category: Injection (OWASP A03) - [ ] All database queries use parameterized statements or ORM query builders — no string concatenation with user input - [ ] No raw SQL strings built from request parameters, headers, or URL segments - [ ] ORM methods that allow raw SQL (e.g., `.raw()`, `.query()`, `execute()`) are absent or reviewed for injection risk - [ ] HTML output is escaped or uses a framework that auto-escapes (no `dangerouslySetInnerHTML`, `innerHTML =`, or template literal injection into DOM) - [ ] Shell commands do not include user input; if unavoidable, input is validated against a strict allowlist - [ ] XML/JSON parse