code-review-and-quality

1# Code Review and Quality
2 
3## Overview
4 
5Multi-dimensional code review with quality gates. Every change gets reviewed before merge — no exceptions. Review covers five axes: correctness, readability, architecture, security, and performance.
6 
7**The approval standard:** Approve a change when it definitely improves overall code health, even if it isn't perfect. Perfect code doesn't exist — the goal is continuous improvement. Don't block a change because it isn't exactly how you would have written it. If it improves the codebase and follows the project's conventions, approve it.
8 
9## When to Use
10 
11- Before merging any PR or change
12- After completing a feature implementation
13- When another agent or model produced code you need to evaluate
14- When refactoring existing code
15- After any bug fix (review both the fix and the regression test)
16 
17## The Five-Axis Review
18 
19Every review evaluates code across these dimensions:
20 
21### 1. Correctness
22 
23Does the code do what it claims to do?
24 
25- Does it match the spec or task requirements?
26- Are edge cases handled (null, empty, boundary values)?
27- Are error paths handled (not just the happy path)?
28- Does it pass all tests? Are the tests actually testing the right things?
29- Are there off-by-one errors, race conditions, or state inconsistencies?
30 
31### 2. Readability & Simplicity
32 
33Can another engineer (or agent) understand this code without the author explaining it?
34…