Comprehensive Code Review

The Problem

Code reviews are essential but inconsistent. Human reviewers miss things when tired, rush through large diffs, or focus only on style while ignoring security. You need a systematic first pass that catches structural issues, security holes, performance traps, and readability problems — before a human reviewer ever sees the code.

The Prompt

Perform a comprehensive code review on the following code. Act as a senior engineer with expertise in security, performance, and clean architecture.

LANGUAGE/FRAMEWORK: [e.g., TypeScript/React, Python/FastAPI, Go]

CODE:
[paste your code here]

Review the code across these 6 dimensions and rate each from 1-5:

1. **Correctness** — Does the logic do what it claims? Are there edge cases or off-by-one errors?
2. **Security** — Any injection vectors, XSS risks, hardcoded secrets, or insecure patterns?
3. **Performance** — Unnecessary re-renders, O(n^2) loops, missing memoization, or N+1 queries?
4. **Readability** — Are names descriptive? Is the flow easy to follow? Any magic numbers?
5. **Maintainability** — Is it modular? Would a new developer understand this in 6 months?
6. **Error Handling** — Are failures handled gracefully? Are errors informative?

For each issue found, provide:
- **Line/Section**: Where exactly the issue is
- **Severity**: critical / warning / suggestion
- **Problem**: What's wrong
- **Fix**: Concrete code change to resolve it

Example Output

## Review Summary: 3.8 / 5.0

| Dimension       | Score | Issues |
|-----------------|-------|--------|
| Correctness     | 4/5   | 1 edge case with empty arrays |
| Security        | 2/5   | SQL injection in search query |
| Performance     | 4/5   | Minor: unnecessary spread in loop |
| Readability     | 4/5   | Good overall, 2 magic numbers |
| Maintainability | 4/5   | Consider extracting validation |
| Error Handling  | 3/5   | Catch blocks swallow errors silently |

### Critical: SQL Injection (Security)
Line 34: `db.query("SELECT * FROM users WHERE name = '" + input + "'")`
Fix: Use parameterized queries: `db.query("SELECT * FROM users WHERE name = $1", [input])`

When to Use

Run this before opening a pull request, after completing a feature, or when inheriting unfamiliar code. It works as a systematic first pass that catches the issues humans commonly miss — especially security vulnerabilities and subtle performance traps.

Pro Tips

• Review in chunks — for files over 200 lines, split into logical sections and review each separately for better accuracy.
• Specify your standards — add “Follow OWASP guidelines” or “Use React best practices” to get framework-specific feedback.
• Use it as a learning tool — ask a follow-up: “Explain why the SQL injection is dangerous and show me how an attacker would exploit it.”