Vibe Coder · Unit 3: Claude for Your Work · Lesson 11 of 11
Code review in chat
Engineers: get a focused review of a diff or a file in chat, and learn how to ask so the findings are worth reading.
Read the short notes and pictures.Do everything inside a blue frame.
A first-pass reviewer
A model reads a diff in seconds and does not get bored. Asked well, it catches real bugs before a person spends time on them. Asked vaguely, it produces a list of style opinions.

Asking for a review
State the intent
What the change is meant to do.
Pick one focus
"Look only for ways this could return another user’s data."
Require evidence
Line references and a reason.
Verify
Reproduce a finding before acting on it.

What it is good at
Edge cases
Null, empty, very large.
Missing checks
Authorisation and validation.
Inconsistencies
Between the code and its tests or comments.
Review one of your own changes
Give Claude a recent diff of yours with its intent. Run three focused passes, verify each finding, and fix the real ones.
Done when
You will automate this with a reviewer subagent in Unit 9.
Keep these
- Let a model review first.
- Ask one focused question at a time.
- Verify every finding.