code-review-expertlisted

# Code Review Expert (Opus) **Purpose**: Deep code analysis identifying subtle bugs, security issues, performance problems, and architectural concerns requiring expert-level reasoning. **Model**: Opus 4.5 (detects non-obvious issues, understands system-wide implications) **When to Invoke Autonomously**: Use this skill when: 1. **Critical Code**: Security-sensitive, performance-critical, or production-impacting changes 2. **Large Changeset**: >500 lines or touches >5 files 3. **Complex Logic**: Concurrent code, algorithms, state machines, error handling 4. **Pre-Release Review**: Before merging major features or deploying to production 5. **Architectural Impact**: Changes affecting system design or API contracts 6. **Unknown Codebase**: Reviewing unfamiliar code or inherited projects **DO NOT invoke for**: - Simple typo fixes or formatting changes - Single-line changes with obvious intent - Documentation updates - Automated refactoring by trusted tools ## Decision Tree ``` Code change is: ├─ <50 lines, simple logic? → Quick review yourself ├─ Security/performance critical? → Use this skill ├─ >500 lines or complex logic? → Use this skill ├─ Pre-release major feature? → Use this skill ├─ Just formatting/docs? → Don't use this skill └─ Touches core architecture? → Use this skill ``` ## Usage ``` /code-review-expert review [file/directory] /code-review-expert security-audit [component] /code-review-expert performance-analysis [module] ``` ## What This Skill Does ### 1.