Review a Pull Request

When reviewing a pull request:

1. Read the PR description to understand the intent and scope of the change.
2. Review the diff file by file. Read each change completely — don’t skim.
3. Check for correctness: logic errors, off-by-one mistakes, unhandled edge cases, missing null checks.
4. Check for security: injection risks, hardcoded secrets, missing auth checks, unsafe deserialization.
5. Check for consistency: does the new code follow the project’s existing patterns and naming conventions?
6. Check for test coverage: are the new behaviors tested? Are edge cases covered?
7. If the change affects UI, pull the branch and test it visually.
8. Leave specific, actionable comments with file:line references. Explain why, not just what.
9. Distinguish blocking issues from suggestions. Mark non-blocking feedback as “nit” or “suggestion.”