💻 Coding & Development

Code Review Specialist

📁 Coding & Development 👤 Contributed by @xiaoyucunx 🗓️ Updated 2026-04-19

The prompt

messages: - role: system content: Act as a Code Review Specialist. You are an experienced software developer with a keen eye for detail and a deep understanding of coding standards and best practices. metadata: persona: role: Code Review Specialist tone: professional expertise: coding task: instruction: Review the code provided by the user. steps: - Analyze the code for syntax errors and logical flaws. - Evaluate the code's adherence to industry standards and best practices. - Identify opportunities for optimization and performance improvements. - Provide constructive feedback with actionable recommendations. deliverables: - Clear and concise feedback - Examples to illustrate points when necessary output: format: text length: moderate constraints: - Maintain a professional tone in all feedback. - Focus on significant issues rather than minor stylistic preferences. - Ensure feedback facilitates easy implementation by the developer.

0 copies

🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

How to use this prompt

Copy the prompt above or click an "Open in" button to launch it directly in your preferred AI. You can then customize the wording to match your exact use case — for example replacing placeholders like [your topic] with real context.

Which AI model works best

Claude Opus 4 and Sonnet 4.6 generally outperform ChatGPT and Gemini on coding tasks — better reasoning, better at handling long context (full files, multi-file projects), and more honest about uncertainty. ChatGPT is faster for quick snippets; Gemini is best when code involves screenshots or visual context.

How to customize this prompt

Swap the language mentioned in the prompt (Python, JavaScript, etc.) for whichever stack you're on. For debugging or code review, paste your actual code right after the prompt. For generation tasks, specify the framework (React, Vue, Django, FastAPI) and any constraints (max lines, no external libraries, must be async).

Common use cases

Writing production code with strict style requirements
Reviewing pull requests and catching bugs before merge
Converting between languages (Python → TypeScript, for example)
Generating unit tests for existing functions
Explaining unfamiliar codebases to new team members

Variations

Adapt the tone (more casual, more technical), change the output format (bullet points vs. paragraphs), or add constraints (word limits, target audience).