| name | code-review |
| description | Systematic checklist for reviewing code quality and correctness |
When reviewing code, work through these categories in order:
- Correctness — Does the logic match the stated intent? Check edge cases, off-by-one errors, and null/empty inputs.
- Clarity — Are names descriptive? Would a new reader understand the code without comments?
- Error handling — Are errors caught at the right level? Do failures surface useful messages?
- Performance — Are there obvious O(n²) loops, unnecessary allocations, or repeated computations?
- Security — Any injection risks, secrets in code, or untrusted input passed to shell/SQL?
- Tests — Does the change come with tests? Do existing tests still make sense?
For each issue found, state: the location, the problem, and a concrete fix or alternative.