For the complete documentation index, see llms.txt. This page is also available as Markdown.

Code Review Checklist

Purpose

Code review protects design, security and maintainability. It is not only a formatting check.

Reviewer Checklist

Correctness

  • Does the code meet the requirement?

  • Are edge cases handled?

  • Are errors handled deliberately?

  • Are assumptions visible?

Design

  • Are responsibilities clear?

  • Are dependencies appropriate?

  • Is the solution simpler than alternatives?

  • Does it fit architecture boundaries?

Security

  • Is authorization enforced?

  • Is input validated?

  • Are secrets protected?

  • Are logs safe?

  • Are dependencies approved?

Testing

  • Are tests meaningful?

  • Do tests cover failure paths?

  • Are integration points tested?

  • Are regression tests included for bugs?

Maintainability

  • Are names clear?

  • Is code cohesive?

  • Is duplication acceptable or should it be removed?

  • Is documentation updated?

Operations

  • Are logs useful?

  • Are metrics/traces affected?

  • Is configuration validated?

  • Is release or migration impact understood?

Approval Standard

Approve only when you would be comfortable maintaining the code or explaining the risk.

Was this helpful?