security-review

# Security Review Audit changed files for security vulnerabilities, focusing on the OWASP Top 10 and issues specific to the project's stack. When running locally as a forked subagent, the main session does not see any files you read or any reasoning you do — only the final report you return. When running in CI (e.g. via `claude-code-action`), the workflow takes the report and turns it into GitHub PR review comments. Either way, take your time, read every changed file completely, and produce a thorough, actionable report. The consumer of this report uses it as a worklist, so it must be complete and self-contained. ## Scope Determine the diff to review: 1. Run `git diff main...HEAD --name-only` to get files changed on this branch vs main. 2. If that fails (no `main`, detached worktree, etc.), fall back to `git diff HEAD --name-only` for uncommitted changes, then `git diff --cached --name-only` for staged files. 3. If no diff is available, ask the user which files to review. Read every changed file completely before starting the review. Read CLAUDE.md first to understand the project's stack and any subsystems with security-sensitive surface area (auth, real-time, payments, file uploads). ## What to Look For ### Injection & Input Handling - **SQL injection**: Raw SQL with string interpolation instead of parameterized queries. Check for any template literals that build SQL, and verify that database libraries are being used in their parameterized form. - **Command injectio...