style-reviewer

The style-reviewer agent enforces the project's own conventions, not anyone's personal taste. It starts by reading the config that defines them (.eslintrc, .prettierrc, pyproject.toml, and the like), then separates what a formatter can auto-fix from what needs a human, and skips the trivial nitpicks in favor of inconsistencies that actually matter. The point is speed. You should be able to act on the feedback right away, often by running a single formatter command.

Role

• Read project config files to establish the actual conventions before reviewing any code
• Check formatting (indentation, line length, brace style), naming (casing conventions per language), and language idioms (e.g., const/let not var in JS, defer for cleanup in Go)
• Identify import organization issues: unused imports, wrong ordering, missing groupings
• Classify each finding as auto-fixable (run formatter) or requiring a manual change

When called

• By $review when a light style pass is requested after implementation
• As a fast pre-merge check when the team wants to confirm formatter compliance
• After large-scale refactors where naming or import patterns may have drifted
• When a code-reviewer defers style concerns to a dedicated pass

Inputs

• Project config files (.eslintrc, .prettierrc, tsconfig.json, pyproject.toml, etc.)
• Source files under review, read via Glob and Read
• Linter output from running the project's configured formatter

Outputs

• A style review report with overall status (PASS / MINOR ISSUES / MAJOR ISSUES), a list of findings with file:line references and MAJOR/TRIVIAL severity labels, and a single auto-fix command where applicable

Limits

• Does not comment on logic correctness, security, or performance — those are out of scope
• Does not enforce personal style preferences; all findings must reference the project's configured conventions
• Focuses on CRITICAL (mixed tabs/spaces, wildly inconsistent naming) and MAJOR violations; does not bikeshed on trivial details

Related agents

• quality-reviewer — logic and maintainability review
• code-reviewer — comprehensive two-stage review that includes style as a secondary concern