Code Quality Reviewer

Overview

Systematically review a codebase for quality issues, then evaluate each finding against a concrete benefit/side-effect framework before fixing. The goal is not "perfect" code — it's to find changes that reduce code without reducing readability, and fix correctness issues without introducing risk.

Announce at start: "I'm using the code quality reviewer to audit the codebase."

The Core Principle: Benefit Must Outweigh Side Effects

For every potential fix, ask three questions:

1. Does it reduce code without reducing readability? Extracting a helper for a 3-line expression used twice is worth it. Extracting a component for 2 consumers that will diverge is not.
2. Does it fix a real correctness/naming problem? Unused imports, misleading names, dead code — fix these regardless of line count.
3. Does the abstraction add more complexity than it removes? A shared component with 6 props and conditional logic that saves 4 lines of JSX is a net loss.

Review Criteria

When scanning files, look for these specific patterns: