A reviewer writes: "nit: variable name `x` could be more descriptive". What does "nit" mean?
"nit" (short for nitpick) signals that the comment is non-blocking and low-priority. Using "nit:" is a professional convention that saves time: the author knows immediately that this is optional feedback. Without "nit:", authors sometimes treat every comment as equally blocking, which slows down reviews and creates unnecessary friction.
2 / 10
Which code review comment is most professional and actionable?
Professional review comments: describe the specific issue (inline parsing in a 60-line function), suggest a concrete alternative (extract to parseUserInput()), explain the benefit (easier to test in isolation), and signal blocking status (non-blocking). "Wrong", "don't like", and "rewrite this" are emotion-based or too vague to act on. Good review comments give the author everything they need to make a decision without coming back to ask clarifying questions.
3 / 10
A reviewer writes "LGTM" on your PR. What does this mean?
LGTM = "Looks Good To Me" — the standard approval phrase in code review. It signals the reviewer has reviewed the changes and approves them without further changes. In GitHub/GitLab, LGTM in a comment may or may not correspond to a formal "Approve" review action — some teams require both.
4 / 10
You disagree with a reviewer's suggestion. Which response is most professional?
Disagreeing professionally: acknowledge the suggestion, explain your reasoning with a specific technical argument, invite further discussion, and explicitly defer if the reviewer is the maintainer. This approach keeps the conversation technical rather than personal, and gives the reviewer enough information to either accept your reasoning or explain why their suggestion is important. Ignoring comments is a red flag for maintainers.
5 / 10
When should a reviewer use "Request changes" vs "Comment" in a GitHub review?
"Request changes" is a formal blocking action — the PR cannot be merged (in most configurations) until the reviewer approves. Use it only for genuine blockers: bugs, security issues, breaking changes, or violations of documented project standards. Using "Request changes" for stylistic preferences or non-blocking suggestions is a power misuse that slows delivery and damages contributor relationships. Use "Comment" for everything that is non-blocking.
6 / 10
Sarah from QA flagged a PR with the comment: 'This seems to be returning an empty array when it should return a list of user objects. Please investigate.' What is Sarah's primary intention in this message?
Sarah isn't asking you to fix the code directly. Instead, she's highlighting a discrepancy between the *expected* outcome (a list of user objects) and what the PR is actually returning (an empty array). Her intention is for you to investigate the root cause of this difference before proceeding with any changes.
7 / 10
During a code review for a new API endpoint, Liam writes in the PR description: 'I've added error handling for invalid input. Please ensure this covers all edge cases.' Which of the following best describes Liam's approach to the review?
Liam's comment isn't a general request for a full overhaul. He's explicitly pointing out an area where further scrutiny is needed – error handling for invalid input and edge cases. This demonstrates proactive guidance during the review process.
8 / 10
You've submitted a PR containing refactoring of a complex function. Mark replies in Slack: 'Looks good! 👍'. What does this response primarily indicate?
'Looks good! 👍' is a common Slack shorthand indicating general approval. It doesn't necessarily mean Mark has reviewed the code in detail or identified any issues. He's expressing satisfaction with the overall appearance and functionality – but you should still verify this yourself.
9 / 10
You've received a code review comment: 'Consider using asynchronous operations here to avoid blocking the main thread.' What is the reviewer *most likely* suggesting?
The suggestion of asynchronous operations is typically driven by concerns about blocking the main thread. Blocking can lead to unresponsive UI or slower performance. The reviewer is pointing out a potential bottleneck and suggesting a solution for improved responsiveness.
10 / 10
During a code review of a new microservice, David writes in the PR description: 'I've implemented the authentication flow. The API responds with a JWT token on successful login.' You believe this explanation is insufficient. What action should you take?
While JWT tokens are common in authentication, a basic description isn't enough. You need to ensure David has addressed potential security vulnerabilities (e.g., token expiration, storage) and error handling scenarios. Requesting changes is the appropriate way to proactively address these concerns.
What will I practise in "🔍 Participating in Code Review"?
This module focuses on Open Source Contribution — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Open Source Contribution exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around open source contribution — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Open Source Contribution exercises?
See the Open Source Contribution hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.