5 exercises on the specific language used in code review comments — nit, elaborate, ready to merge, flagging issues, and awaiting review. Professional communication patterns that native reviewers use every day.
0 / 5 completed
1 / 5
A reviewer leaves the following comment on a variable name: "___ : could rename this to `isLoading` for clarity — feel free to ignore."
Which label correctly marks this as a minor, optional suggestion?
Nit (short for "nitpick") is the standard label for minor, optional, non-blocking comments in code reviews.
Using "nit" signals:
The comment is cosmetic — it does not affect correctness or functionality
The developer can choose to address it or not before merging
The reviewer is not blocking the PR over this
Common nit examples:
"nit: extra blank line here"
"nit: variable name could be more descriptive"
"nit: trailing comma in the array"
Review comment severity ladder:
nit / nitpick — cosmetic, optional
suggestion — recommended but non-blocking
question — asking for clarification
blocker / must-fix — must be resolved before merge
CRITICAL / SECURITY — urgent, dangerous
2 / 5
A reviewer is curious about a design choice and writes: "Could you ___ on why you chose a Map here instead of a plain object?"
Which verb naturally completes this professional code review question?
Elaborate is the most natural and professional verb for asking someone to provide more detail or explanation.
Collocations with "elaborate":
"Could you elaborate on this approach?"
"Please elaborate — I don't fully understand the rationale."
"Can you elaborate on the trade-offs?"
Why not the others?
expand on — also natural and acceptable: "Could you expand on this?" is correct English, though slightly less formal than "elaborate"
extend on — not a natural English collocation; "extend" does not collocate with "on" in this way
grow on — completely wrong in this context; "grow on you" is an idiom meaning to become more appealing over time
Alternatives: "Could you add more context?", "What was the reasoning behind this choice?", "Can you walk me through the thinking here?"
3 / 5
A reviewer has reviewed the code and has no issues. They write: "This looks great — ___ to merge."
Which word is the most natural completion?
Ready to merge is the standard professional phrase for communicating that a PR has passed review and can be merged.
Common approval phrases:
"Ready to merge." — the most neutral, widely used signal
"LGTM" — "Looks Good To Me" — the most common informal shorthand for approval
"Approved ✓"
"Looks good — merging now." — when the reviewer also merges
"Good work! Approved."
Why not the others?
"free to merge" — grammatically valid but less idiomatic for code reviews
"cleared to merge" — used in some teams, especially those from military or aviation-influenced cultures; acceptable but less common
"allowed to merge" — not natural; sounds like a permission statement rather than a review outcome
GitHub LGTM culture: Many teams use LGTM in comments and only click the formal Approve button when branch protection requires it.
4 / 5
A reviewer writes: "I've ___ a few issues that should be addressed before this goes to production."
Which verb is the most natural and professional fit?
Flagged is the most idiomatic and professional verb in a code review context — it implies the reviewer has explicitly called out issues for attention, not just noticed them passively.
Verb nuances:
flag — to call out, highlight, or mark something for attention; active and purposeful. Perfect in professional written communication: "I've flagged a few concerns."
raise — also excellent: "I've raised a few issues" implies formally bringing them to attention
spot / notice / find — more passive verbs; they describe the act of discovery but not the act of communicating it professionally
Related patterns:
"I've flagged a potential memory leak in the explanation."
"I raised a concern about the error handling."
"A few things I flagged in the diff — see inline comments."
Note: "Found" and "spotted" are not wrong — they simply sound less professional in written review communication than "flagged" or "raised".
5 / 5
A developer checks the PR status and writes: "This PR is ___ a security review from the AppSec team before it can be merged."
Which verb phrase is most natural?
Awaiting is the most natural and professional choice — it precisely expresses that the PR is in a waiting state, dependent on the AppSec team's action.
Verb comparison:
awaiting — active, professional: "The PR is awaiting AppSec review." Commonly used in written communication and PR status updates.
pending — also correct and widely used: "Pending security review." Often seen as a status label in Jira or PR descriptions. Slightly more formal/static.
needing — grammatically correct but less professional; sounds informal
requiring — grammatically correct but more bureaucratic and less natural as a status description
What does the "Code Review Comment Collocations" exercise practise?
5 exercises on the specific language used in code review comments — nit, elaborate, ready to merge, flagging issues, and awaiting review. Professional communication patterns that native reviewers use every day.
How many questions are in this exercise?
This exercise has 5 questions, each multiple-choice with an explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse Code Review Collocations for a related exercise to start with instead.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct collocation and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Code Review Comment Collocations" part of a larger series?
Yes — it's one exercise in Code Review Collocations. See that category page for the full list of related collocation exercises.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See Code Review Collocations for related exercises, or browse the main Collocations hub for other IT English word pairings.