NEW: English for Tech Bundle → Save 40%
Speak Tech English

Code Reviews & PRs

English for Code Reviews and Pull Requests

Code-review English must be precise and polite. This hub teaches softeners, blocking vs optional comments, and PR vocabulary so B2 engineers can give feedback that lands well. Start with phrase patterns like “nit:”, “optional:”, and “Have you considered…?” before writing your next review.

Named packs

Start with these review kits

Soft feedback, bug/incident English, and listening practice for pull requests — the phrases senior engineers actually use.

Most popular

Start with these terms

High-demand lessons with a short definition — open the full page for examples and practice.

More resources

Frequently asked questions

How do I give critical feedback in a code review politely?
Separate tone from the request: “Thanks for this — one concern on the error handling. Could we add a null check here?” Use “we” and questions for optional changes; be direct only for blocking issues.
What does LGTM mean in a pull request?
LGTM means “Looks good to me” — approval to merge (sometimes with minor nits). Pair it with any remaining comments so the author knows what is still required.
How should I write a pull request description in English?
State why, what changed, and how to test. Example: “Adds rate limiting to the public API to reduce abuse. Test: hit /v1/search 100 times and confirm 429 responses.”
What’s the difference between a nit and a blocking comment?
A nit is a small, non-blocking preference (naming, style). A blocking comment must be fixed before merge. Labelling them helps non-native authors prioritise.

Related topics

See all topics
← Back to the Knowledge Base

Want a structured course? English for Developers bundle.