Back to guide/Developer Tools

Deep Code Review

Claude's precise instruction following produces consistently structured reviews. Gemini handles this well too, especially with its large context window for reviewing longer files.

claude-vs-geminilanguageproject_typearchitecture_pattern
Edit View
Prompt
Review the following {{language}} code for a {{project_type}} project.

Analyze it across these dimensions:

1. **Correctness**: Identify any bugs, logic errors, or unhandled edge cases
2. **Architecture**: Does this follow {{architecture_pattern}} principles? Flag violations with specific fixes
3. **Performance**: Note any O(n^2) or worse operations, unnecessary allocations, or missed caching opportunities
4. **Security**: Check for injection vulnerabilities, improper input validation, or leaked secrets
5. **Readability**: Suggest naming improvements and identify overly complex functions (>30 lines)

For each issue found:
- Severity: Critical / Warning / Suggestion
- Line reference or code snippet
- Concrete fix (show the corrected code, not just a description)

End with a summary: "X critical, Y warnings, Z suggestions" and an overall quality score out of 10.

Variables to customize

{{language}}{{project_type}}{{architecture_pattern}}

Why this prompt works

Claude's precise instruction following produces consistently structured reviews. Gemini handles this well too, especially with its large context window for reviewing longer files.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.

Related prompts

Code Review Assistant

Get thorough code reviews with actionable feedback tailored to your language, framework, and standards.

Context-Aware Code Completion

Providing the surrounding code and project context lets the model match existing patterns exactly. The constraint against modifying existing code prevents unwanted side effects.

Inline Code Suggestion

Constraining suggestions to match existing style and scope produces insertions that feel native to the codebase. The 'no explanation' rule mimics real inline completion behavior.

Code Explanation

The audience level parameter adjusts complexity automatically. Requiring a usage example ensures the explanation is practical, not just theoretical.