code-review

Review code across five dimensions and produce a prioritized list of findings. Suggest improvements; don't demand them. Praise good patterns alongside issues.

Step 1: Read the Code

Understand intent before judging implementation. Before writing a single finding:

• Identify the purpose of the change (feature, fix, refactor, test).
• Note the architectural context (framework, patterns, conventions in use).
• Read related tests and documentation if available.
• If reviewing a PR, read the description and linked issues first.

Step 2: Review Across Five Dimensions

Evaluate the code against each dimension using the specific checks below.

Correctness