Review mode for code review, security audit, and best practices check. Use when user asks for code review or quality assessment. Evaluates code quality, identifies issues by severity, and suggests improvements with positive feedback.
Goal: Evaluate code quality, identify issues, and suggest improvements.
## REVIEW: [Component/Feature name]
**Scope:** [What was reviewed]
**Language:** [JS/Python/Java/Go/PHP/Ruby]
**Overall:** [Good / Needs Work / Critical Issues]
---
### Summary
| Category | Status |
|----------|--------|
| Functionality | OK / Warning / Error |
| Code Quality | OK / Warning / Error |
| Security | OK / Warning / Error |
| Performance | OK / Warning / Error |
| Maintainability | OK / Warning / Error |
---
### Issues Found
#### Critical
| Issue | Location | Suggestion |
|-------|----------|------------|
| [Description] | `file:line` | [How to fix] |
#### Important
| Issue | Location | Suggestion |
|-------|----------|------------|
| [Description] | `file:line` | [How to fix] |
#### Minor / Suggestions
| Issue | Location | Suggestion |
|-------|----------|------------|
| [Description] | `file:line` | [How to fix] |
---
### What's Done Well
- [Positive point 1]
- [Positive point 2]
---
### Recommended Actions
1. [ ] [Action 1] - Priority: High
2. [ ] [Action 2] - Priority: Medium
3. [ ] [Action 3] - Priority: Low
any, raw Object, interface{} abuse)| Level | Description | Action Required |
|---|---|---|
| Critical | Security vulnerability, data loss, crash | Must fix before merge |
| Important | Bug, bad practice, tech debt | Should fix soon |
| Minor | Style, optimization, nice-to-have | Optional improvement |
| DON'T | DO |
|---|---|
| Only criticize | Balance with positive feedback |
| Be vague ("this is bad") | Be specific with location and fix |
| Focus on style only | Prioritize functionality and security |
| Rewrite everything | Suggest minimal effective changes |
| Skip context | Understand purpose before reviewing |