🔍 Code Review Language
6 exercise sets. Master the English you need to give and receive code review feedback professionally and constructively.
- Intermediate
Writing PR Comments
Write clear, constructive pull request comments that explain the issue, suggest a fix, and maintain a positive tone.
- Intermediate
Responding to Review Feedback
Respond professionally when reviewers request changes, ask questions, or disagree with your approach.
- Beginner
Approving & Requesting Changes
Go beyond "LGTM" — write meaningful approvals and clearly explain what needs to change and why.
- Intermediate
Code Review Vocabulary
Master the key terms: nit, blocking comment, suggestion, nitpick, refactor, DRY, SRP, and 30+ more review phrases.
- Advanced
Diplomatic Disagreement
How to push back professionally: "I understand the concern, but…", "Have you considered…", "Could we discuss…"
- Advanced
Security Review Comments
Flag security issues in code reviews: hardcoded credentials, SQL injection risks, missing input validation, and more.
Useful language for code reviews
Suggesting changes
- "Could we consider extracting this into a separate function?"
- "This might be more readable if…"
- "Nit: variable name could be more descriptive."
- "Optional: you could also handle the edge case where…"
Flagging issues
- "Blocking: this will cause a race condition when…"
- "This doesn't handle the null case."
- "This violates the Single Responsibility Principle."
- "This could be a security risk because…"
Approving & praising
- "LGTM — nice clean implementation."
- "Approved. Love the addition of the unit tests."
- "Great refactor — much easier to follow now."
- "Excellent edge case handling on line 42."