code-review-expertlisted

# Code Review Expert ## Overview Perform 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. ## Severity Levels | Level | Name | Description | Action | |-------|------|-------------|--------| | **P0** | Critical | Security vulnerability, data loss risk, correctness bug | Must block merge | | **P1** | High | Logic error, significant SOLID violation, performance regression | Should fix before merge | | **P2** | Medium | Code smell, maintainability concern, minor SOLID violation | Fix in this PR or create follow-up | | **P3** | Low | Style, naming, minor suggestion | Optional improvement | ## Workflow ### 1) Preflight context - Use `git status -sb`, `git diff --stat`, and `git diff` to scope changes. - If needed, use `rg` or `grep` to find related modules, usages, and contracts. - Identify entry points, ownership boundaries, and critical paths (auth, payments, data writes, network). **Edge cases:** - **No changes**: If `git diff` is empty, inform user and ask if they want to review staged changes or a specific commit range. - **Large diff (>500 lines)**: Summarize by file first, then review in batches by module/feature area. - **Mixed concerns**: Group findings by logical feature, not just file order. ### 2) SOLID + architecture smells - Load `references/solid-checklist.md` for specific prompts. - Look for: - **SRP**: Overload