Review
Audit diffs for correctness, security, and readiness before shipping.
Diff review A focused correctness pass on the change you just made. Review review correctness
Review my current diff for correctness bugs and edge cases only. List findings by severity (high/medium/low). Skip style nits and formatting. Explain-back Understand unfamiliar code and catch surprises in it. Review understanding review
Explain what @<file> does in plain language, step by step. Then flag anything that looks unintentional or inconsistent with the rest of the module. Performance sniff Catch scaling problems before they hit production. Review performance review
Scan @<file> for performance issues that matter at scale — N+1 queries, needless allocations in hot paths, blocking calls in async code. Only flag things with real impact, and estimate the cost of each. PR-ready check Self-review a PR the way a demanding reviewer would. Review review testing
Act as a strict reviewer. Does this change actually do what the PR description claims? Call out untested paths, missing error handling, and anything that would block approval. Security pass A targeted security review of sensitive code. Review security audit
Audit @<file> for injection, auth, and secret-handling issues. For each finding give the concrete risk, a reproduction path, and a specific fix. Ignore theoretical issues that can't happen given how it's called. No prompts match your filters.