Request a Code Review with Context
Added 2026-11-04
Say what changed, why, and where to look hardest.
I need a colleague to review some code (context below). Write the request: 1) one line on purpose and scope; 2) why this design, including alternatives considered; 3) three places to focus on; 4) known risks or unfinished parts; 5) how to verify or reproduce; 6) what not to worry about this time — formatting, naming. Under 150 words, ready to paste into the PR description.
Site original
Chinese original
How to use
评审请求写得越具体，收到的意见越有用。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.