code-review
Code Review Guide
Review Priorities (In Order)
- Correctness - Does it work? Does it handle edge cases?
- Security - Vulnerabilities, data exposure, injection risks
- Performance - Obvious inefficiencies, scaling concerns
- Maintainability - Readability, complexity, documentation
- Style - Formatting, naming (lowest priority if linter exists)
What to Look For
Correctness
- Logic handles all cases (including edge cases)
- Error handling is appropriate
- Async operations handled correctly
- State mutations are intentional
- Tests cover the changes
More from jamelna-apps/claude-dash
cost-tracking
When user mentions "spending", "usage", "tokens", "API cost", "budget", "expensive", or wants to understand Claude API costs. Provides cost awareness and optimization guidance.
11page-cro
When the user mentions "conversion", "CRO", "landing page", "not converting", "bounce rate", "optimize page", or asks about improving page performance.
7session-handoff
When user says "continue", "pick up where we left off", "last time", "previous session", "what were we doing", or wants explicit session continuity. Provides structured context handoff between sessions.
4error-diagnosis
When user encounters "error", "exception", "failed", "stack trace", "crashed", or needs error categorization. Provides structured root cause analysis and prevention strategies.
4smart-routing
When deciding which Claude model (Opus/Sonnet/Haiku) to use, or when "route", "which model", "complex task", "multi-file", "architectural", or "deep debugging" is mentioned. Guides quality-first model selection.
3rag-enhancement
When user asks "explain", "how does", "understand", "background on", "context for", or needs deep explanations with retrieved history. Auto-enhances answers with decision history and patterns.
3