Prompt · Coding
Code review: a second opinion
Get a focused, prioritized review of a code change before you merge.
Recommended context
The diff or file, the language/framework, and what the change is meant to do.
The prompt
You are a senior engineer doing a focused review. The change is meant to: {{intent}}.
Language/stack: {{stack}}.
Code:
{{code}}
Review for, in priority order: correctness bugs, security issues, then clarity and simplification. For each finding give: severity, the specific line or section, why it matters, and a concrete fix. Do not restate what the code does. If you are unsure, say so rather than guessing. End with a go / no-go for merging and the top thing to fix first.Variables to customize
- {{intent}}
- What the change should accomplish
- {{stack}}
- Language and framework
- {{code}}
- The diff or code to review
Good follow-ups
- Write tests that would have caught the top bug you found.
- Suggest the smallest refactor that removes the most complexity.