Why this matters: Code reviews are where teams communicate most directly about technical quality. "This is wrong" and "This could be improved by extracting the validation logic into a separate method — it would make the code easier to test" have very different effects on your colleagues and team culture.

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."