Code review guidelines are typically tailored to the specific requirements of a project, taking into consideration the balance between code quality and project deadlines.

But generally, you are expected when reviewing code to:

1. Identify and report bugs
2. Improving code quality

Bugs can be incorrect logic, spec misunderstanding. Missing edges cases are quite frequent.
Code review is expected to improve code quality since it gives another perspective on a piece of code.
It's the opportunity to make sure that the code is

- maintenable, easy to understand for others, consistent with the overall project.
- efficient, fast and lightweight on resource usage.


Bad reviews tend to focus on style rather than substance.
Generally priority should be given to:
- making sure that the code works
- that the specification requirements are met
- that edge cases are properly handled
- *then* improving code quality and performance
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence