AI Prompts for Claude for Code Review

Review this code for correctness: [PASTE CODE]. Look for logic errors, off-by-one errors, incorrect assumptions, and cases where the code will not behave as the developer intends.

This function claims to do [DESCRIBED BEHAVIOR]. Does it actually do that? [PASTE CODE]. Walk through the logic with a few concrete inputs and show where it succeeds or fails.

Find the bugs in this code: [PASTE CODE]. Do not just list them, explain why each is a bug and what the correct behavior should be.

Review this code for edge cases that are not handled: [PASTE CODE]. What inputs, states, or sequences will cause unexpected behavior? What should happen in each case?

I wrote this code to solve [PROBLEM]: [PASTE CODE]. Is this the right solution? Are there cases where it will give wrong answers, infinite loops, or incorrect state?

Review this code for security vulnerabilities: [PASTE CODE]. Check for: injection risks, improper input validation, authentication/authorization issues, data exposure, and insecure dependencies.

This code handles user input: [PASTE CODE]. Is it sanitizing and validating correctly? What injection or manipulation attacks does it leave open?

Review this authentication / authorization code: [PASTE CODE]. What security assumptions is it making? Where could it be bypassed or manipulated?

This code handles sensitive data (passwords, tokens, PII): [PASTE CODE]. Is it storing, transmitting, and handling it securely? What should be changed?

Review this API endpoint for security issues: [PASTE CODE]. Check authentication, rate limiting, input validation, error message information leakage, and CORS configuration.

Review this code for performance issues: [PASTE CODE]. Identify O(n²) or worse algorithms, unnecessary database queries, blocking operations, and memory inefficiencies. Suggest concrete improvements.

This code makes database calls: [PASTE CODE]. Is it making N+1 queries? Are queries properly indexed? Is it fetching more data than needed? What are the performance risks at scale?

Review this code for memory usage issues: [PASTE CODE]. Are there memory leaks, large objects kept in memory unnecessarily, or patterns that will not scale?

This is a hot path that runs [FREQUENCY]: [PASTE CODE]. What would you optimize first? What is the likely bottleneck at [EXPECTED LOAD]?

Compare these two implementations and explain which performs better and why: [PASTE IMPLEMENTATION A] vs [PASTE IMPLEMENTATION B].

Review this code for maintainability: [PASTE CODE]. Is it easy to understand, modify, and extend? What would make it harder to maintain six months from now?

Review this PR diff for adherence to these standards: [PASTE STANDARDS OR DESCRIBE THEM]. Flag every violation with the specific line and the applicable rule.

This code will be maintained by a team. Review it for: naming clarity, appropriate abstraction level, documentation of non-obvious logic, and consistency with common patterns.

This code has too much complexity. Suggest how to simplify it without losing functionality: [PASTE CODE]. Break it down into the specific changes that would have the most impact on readability.

Write a code review comment for this code as if you were a senior engineer giving feedback to a junior. Be specific, educational, and constructive: [PASTE CODE].