code-review-expert

1# Code Review Expert
2 
3## Overview
4 
5Perform a structured review of the current git changes with focus on SOLID, architecture, removal candidates, and security risks. Default to review-only output unless the user asks to implement changes.
6 
7## Severity Levels
8 
9| Level | Name | Description | Action |
10|-------|------|-------------|--------|
11| **P0** | Critical | Security vulnerability, data loss risk, correctness bug | Must block merge |
12| **P1** | High | Logic error, significant SOLID violation, performance regression | Should fix before merge |
13| **P2** | Medium | Code smell, maintainability concern, minor SOLID violation | Fix in this PR or create follow-up |
14| **P3** | Low | Style, naming, minor suggestion | Optional improvement |
15 
16## Workflow
17 
18### 1) Preflight context
19 
20- Use `git status -sb`, `git diff --stat`, and `git diff` to scope changes.
21- If needed, use `rg` or `grep` to find related modules, usages, and contracts.
22- Identify entry points, ownership boundaries, and critical paths (auth, payments, data writes, network).
23 
24**Edge cases:**
25- **No changes**: If `git diff` is empty, inform user and ask if they want to review staged changes or a specific commit range.
26- **Large diff (>500 lines)**: Summarize by file first, then review in batches by module/feature area.
27- **Mixed concerns**: Group findings by logical feature, not just file order.
28 
29### 2) SOLID + architecture smells
30 
31- Load `references/solid-checklist.md` for specific prompts.
32- Look for:
33…