Good review comments are specific, actionable, and framed around the code, not the person who wrote it. The best comments move the PR forward. The worst ones create confusion, defensiveness, or noise.
What a good comment looks like
- It identifies the exact issue.
- It explains why the issue matters.
- It suggests a next step, not just criticism.
What to avoid
- Vague comments like “this looks wrong” without context
- Style debates disguised as blockers
- Long threads on minor issues while the real risk goes unaddressed
- Comments that sound personal instead of technical
A simple structure
- State the problem.
- Explain the impact.
- Suggest a fix or ask a focused question.
That format keeps comments short and useful. It also makes it easier for the author to respond without guessing what the reviewer wanted.