code-review-expertlisted

# Code Review Expert Checklists Provides structured review workflow and reference checklists for the code-reviewer agent. ## 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 | ## Review Workflow ### Step 1: Preflight Context - Run `git status -sb`, `git diff --stat`, and `git diff` to scope changes - Use `git diff --cached` to include staged changes - If needed, use Grep to find related modules, usages, and contracts **Edge cases:** - **No changes**: Inform user, 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 ### Step 2: SOLID + Architecture Smells Load `references/solid-checklist.md` for detailed prompts. Look for SRP/OCP/LSP/ISP/DIP violations and common code smells. When proposing refactor, explain *why* it improves cohesion/coupling. Non-trivial refactors get incremental plans, not large rewrites. ### Step 3: Removal Candidat