How to run automated code review with Claude Code — using /review, /ultrareview, and /security-review.
Reads all files changed on the current branch vs. main. Returns a structured review: logic bugs, security flags, style issues, missed edge cases, and API misuse — with severity levels and concrete fix suggestions.
| Command | Best for | How it works | Notes |
|---|---|---|---|
| /review | Standard PR review | Single model, current branch vs. main | Free, fastest |
| /ultrareview | Critical merges, large PRs | Multiple agents in parallel — security, logic, style, tests each get dedicated analysis | Billed separately; use /ultrareview 123 for GitHub PR #123 |
| /security-review | Auth, payments, user input | OWASP Top 10 focused — injection, auth bypass, unsafe deps, insecure defaults | Free; run before any deploy touching user data |
Type /review at the start of a message in any Claude Code session while on a feature branch. Claude Code will automatically diff against your main branch and analyze all changed files.
/review
/ultrareview 42
/loop 10m /review
Off-by-one errors, null dereferences, incorrect loop termination, wrong operator precedence, control-flow issues that only surface in edge cases.
SQL/command injection vectors, missing input sanitization, insecure direct object references, hardcoded credentials, missing auth checks on routes.
Incorrect use of external library APIs, missing required cleanup (file handles, DB connections), wrong concurrency patterns (race conditions, deadlocks in async code).
Inconsistent naming, overly complex functions that should be extracted, dead code, missing tests for new logic.
Use /loop to run /review continuously as you code. Combine with /schedule to set up daily automated branch reviews.
/loop 15m /review
/schedule run /security-review on this branch every night at 11pm
See /review, /security-review, /ultrareview, /loop and 18 more skills — searchable, with examples.
Open Claude Skills Browser →/ultrareview for the current branch, or /ultrareview 123 to review GitHub PR #123. It is billed separately from regular Claude usage./review for standard PR review — quick single-model analysis. Use /ultrareview when you need deeper parallel coverage for critical merges or large PRs. Use /security-review when changes touch auth, payments, user data, or input parsing — it focuses exclusively on OWASP Top 10 and security-critical patterns./loop to run /review on a recurring interval while you're coding: /loop 10m /review runs a review every 10 minutes. For CI-style automation, /schedule can run /review on a cron schedule. Use /update-config to add hooks that trigger /review on specific events.← All slash commands | Automating tasks with /loop & /schedule →