AI Prompts for ChatGPT for Code Review

Review this code for overall quality: [PASTE CODE]. Check for: bugs, edge cases, security issues, readability, and anything that would fail a production code review. Prioritize by severity.

Review this code specifically for [SECURITY VULNERABILITIES / PERFORMANCE ISSUES / EDGE CASES / READABILITY]: [PASTE CODE]. Be specific and give line-level feedback.

Review this code change: [PASTE THE DIFF OR DESCRIBE WHAT CHANGED]. Is the change correct? Are there bugs or missing edge cases? Is the approach appropriate for the goal?

Create a code review checklist for [TYPE OF CODE: REST API / REACT COMPONENTS / DATABASE QUERIES / BACKGROUND JOBS]. What should every reviewer check for in this type of code?

Review this code against these standards: [LIST YOUR STANDARDS OR CODING PRINCIPLES]. Flag specific violations and suggest what to change.

Find logic bugs in this code: [PASTE CODE]. For each bug, show the line, what it currently does, what it should do, and how to fix it.

What edge cases does this code not handle: [PASTE CODE]? For each, describe what would happen and how to handle it.

Review this code for security vulnerabilities: [PASTE CODE]. Check for: injection attacks, authentication issues, sensitive data exposure, insecure operations, and OWASP Top 10 issues.

Review this code for performance problems: [PASTE CODE]. Look for: N+1 queries, inefficient loops, missing indexes, unnecessary re-renders, and blocking synchronous operations.

Review the error handling in this code: [PASTE CODE]. What errors are not handled? What fails silently? What error messages are too vague to diagnose a problem?

Review the readability of this code: [PASTE CODE]. Which parts would confuse a new developer? Flag unclear names, complex logic, and functions that are too long.

Review these tests: [PASTE TESTS AND IMPLEMENTATION]. Are they testing the right things? What is not covered? Would these tests catch the most likely bugs?

Is this code over-engineered for the problem it solves: [PASTE CODE]? What abstractions or complexity can be removed while still meeting the requirements?

Review the function/API design in this code: [PASTE CODE]. Are the interfaces intuitive? Are function signatures clear? Is there anything a consumer would find confusing?

Compare this new code to this existing code: [PASTE BOTH]. Is the new code consistent in style, naming, and patterns? What would need to change to fit in?

Help me write constructive code review feedback for this issue: [DESCRIBE THE ISSUE]. Write it professionally, explaining the why, not just the what.

Write code review inline comments for these specific sections: [PASTE CODE WITH SECTIONS HIGHLIGHTED]. Each comment should be clear, specific, and actionable.

Write a code review summary for these findings: [LIST FINDINGS]. Give a high-level view, categorize by severity, and set clear expectations for what must change.

Write a code review approval comment for this PR: [DESCRIBE THE PR]. It is ready to merge but I want to leave helpful non-blocking suggestions. Approve clearly while leaving the door open for improvements.

I need to request changes on this code. Issues: [LIST ISSUES]. Write the request-for-changes comment professionally, explaining each issue without sounding like a rejection.