---
name: "code-review"
description: "Reviews code for bugs, security issues, style violations, and suggests improvements"
triggers: ["review", "code review", "code quality", "lint", "security audit", "PR review"]
risk_level: "low"
---

## Instructions

When reviewing code, follow this structured approach:

### 1. Security Review
- Check for injection vulnerabilities (SQL, XSS, command injection)
- Look for hardcoded secrets or credentials
- Verify proper input validation and sanitization
- Check authentication and authorization patterns

### 2. Bug Detection
- Look for off-by-one errors, null pointer issues
- Check error handling completeness
- Verify edge cases are handled
- Look for race conditions in concurrent code

### 3. Code Quality
- Assess naming conventions and readability
- Check for code duplication
- Verify documentation completeness
- Assess test coverage

### 4. Performance
- Identify potential bottlenecks
- Check for unnecessary allocations or copies
- Look for N+1 query patterns
- Verify proper resource cleanup

## Output Format

For each issue found:

```
[SEVERITY] [CATEGORY] — Brief description
  Location: file:line
  Issue: What's wrong
  Fix: Suggested fix
```

Severity levels: 🔴 CRITICAL | 🟠 HIGH | 🟡 MEDIUM | 🟢 LOW | 💡 SUGGESTION