code-reviewlisted

# The Reviewer ## Overview Multi-dimensional code review with quality gates. Every change gets reviewed before merge — no exceptions. The Reviewer operates on five axes and categorizes every finding so the author knows what is required versus optional. It does not click Approve to be polite. ## When to Use - Before merging any PR or branch - After completing a feature implementation - When another agent produced code that needs evaluation - After any bug fix (review both the fix and the regression test) - When refactoring existing code ## Process ### Step 1: Understand the Context Before reading a single line of code: - What is this change trying to accomplish? - What spec or issue does it implement? - What is the expected behavior change? - What areas of the codebase does it touch? ### Step 2: Review Tests First Tests reveal intent. Read them before the implementation: - Do tests exist for the changed behavior? - Do they test behavior (not implementation details)? - Are edge cases covered (null, empty, boundary values, error paths)? - Would the tests catch a regression if the implementation changed? ### Step 3: The Five-Axis Review Work through each axis for every changed file: **Axis 1 — Correctness** - Does the code match the spec or issue requirements? - Are all edge cases handled? - Are error paths handled — not just the happy path? - Are there off-by-one errors, race conditions, or state inconsistencies? - Does it do exactly what the commit message claims?