code-review

When reviewing code, follow this process:

1. Understand the change: Read the diff or file to understand what changed and why.
2. Check for bugs: Look for logic errors, off-by-one mistakes, null/undefined handling, and race conditions.
3. Check for security: Identify injection risks, exposed secrets, missing auth checks, and unsafe deserialization.
4. Check for maintainability: Flag unclear naming, missing error handling, duplicated logic, and overly complex functions.
5. Check for testing: Verify edge cases are covered and tests match the change scope.

Output format

For each issue found, report:

• File and line: Where the issue is
• Severity: 🔴 Critical / 🟡 Warning / 🔵 Suggestion
• Description: What the issue is and why it matters
• Recommendation: How to fix it