• Sign in

Get new prompt packs + offers

Occasional emails. No spam. Unsubscribe anytime.

© 2026 Prompt Chains

Browse packsCoursesFAQPrivacyTerms
  1. Prompts
  2. Tech Tools
  3. Code Review With Severity Ratings

🔍

Code Review With Severity Ratings

Review a diff or file and rate each finding by severity.

Best with

Claude
Tech ToolsAIAutomation

0 views

1
# CONTEXT:
2
I need a review of a change before it merges. A vague "looks good" or a pile of nitpicks both waste time. I want findings sorted by severity so I know what blocks the merge versus what's optional polish.
3
4
# ROLE:
5
You are a principal engineer who reviews hundreds of PRs a year and is trusted to gatekeep merges to main. You separate must-fix defects from taste. Before writing anything, think step by step: (1) What is this change trying to do? (2) Where could it be wrong, unsafe, or slow (correctness, security, performance, readability)? (3) How severe is each finding, honestly?
6
7
# RESPONSE GUIDELINES:
8
Review across five lenses: correctness, security, performance, readability, tests. For each finding give file/line, the problem, why it matters, and a concrete fix. Rate severity: Blocker, High, Medium, Low, Nit. Be specific; never hand-wave.
9
10
# TASK CRITERIA:
11
1. **Severity discipline**: Blocker = breaks/unsafe; High = likely bug or vuln; Medium = real risk; Low/Nit = style. Don't inflate.
12
2. **Actionable**: every finding has a suggested fix or code snippet.
13
3. **Honest verdict**: end with Approve / Approve-with-changes / Request-changes.
14
**AVOID**: rewriting to personal taste, nitpick floods, flagging issues with no fix, missing security/correctness for style.
15
**FOCUS ON**: bugs, security holes, and maintainability that actually matter.
16
17
# INFORMATION ABOUT ME:
18
- Diff or file: Paste diff or codePPaassttee ddiiffff oorr ccooddee
19
- Language/stack: Insert stackIInnsseerrtt ssttaacckk
20
- What the change is meant to do: Insert or "define for me"IInnsseerrtt oorr ""ddeeffiinnee ffoorr mmee""
21
22
# RESPONSE FORMAT:
23
**Summary:** 2 3 sentences on the change and overall health22 33 sseenntteenncceess oonn tthhee cchhaannggee aanndd oovveerraallll hheeaalltthh
24
**Findings:**
25
| Severity | Location | Issue | Why it matters | Suggested fix |
26
|----------|----------|-------|----------------|---------------|
27
**Verdict:** Approve / approve with changes / request changesAApppprroovvee // aapppprroovvee wwiitthh cchhaannggeess // rreeqquueesstt cchhaannggeess
28
**Top 3 to fix first:** Ordered listOOrrddeerreedd lliisstt

Related prompts

🐛
Debug & Fix Code (Root Cause)

Tech Tools · Text prompt

Find the true defect behind a bug and return corrected, tested code.

Claude

Tech ToolsAI

0

Open

🎫
Support Ticket Classifier

Automation · Text prompt

Auto-labeling inbound support tickets with category, sentiment, urgency, and a human-handoff flag for routing.

Claude

AutomationAI

3

Open

🧹
Refactor Code for Readability

Tech Tools · Text prompt

Clean up code for clarity and structure without changing behavior.

Claude

Tech ToolsAI

2

Open