/smart-review
Auto-suggest optimal role and approach. Trigger with "review this", "check code quality", "best approach?", "how to improve?".
$ npx -y skills add wasabeef/claude-code-cookbook --skill smart-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/smart-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
Auto-suggest optimal role and approach. Trigger with "review this", "check code quality", "best approach?", "how to improve?".
SKILL.md
smart-review.SKILL.mddescription: 'Auto-suggest optimal role and approach. Trigger with "review this", "check code quality", "best approach?", "how to improve?".'
allowed-tools:
- Read
- Grep
- Glob
Auto-suggest optimal role and approach
A command that analyzes the current situation and automatically suggests the optimal role and approach.
Usage
/smart-review # Analyze current directory
/smart-review <file/directory> # Analyze specific target
Automatic Analysis Logic
Analysis by File Extension
- `package.json`, `*.tsx`, `*.jsx`, `*.css`, `*.scss` → **frontend**
- `Dockerfile`, `docker-compose.yml`, `*.yaml` → **architect**
- `*.test.js`, `*.spec.ts`, `test/`, `__tests__/` → **qa**
- `*.rs`, `Cargo.toml`, `performance/` → **performance**
Security-related File Detection
- `auth.js`, `security.yml`, `.env`, `config/auth/` → **security**
- `login.tsx`, `signup.js`, `jwt.js` → **security + frontend**
- `api/auth/`, `middleware/auth/` → **security + architect**
Complex Analysis Patterns
- `mobile/` + `*.swift`, `*.kt`, `react-native/` → **mobile**
- `webpack.config.js`, `vite.config.js`, `large-dataset/` → **performance**
- `components/` + `responsive.css` → **frontend + mobile**
- `api/` + `auth/` → **security + architect**
Error/Problem Analysis
- Stack traces, `error.log`, `crash.log` → **analyzer**
- `memory leak`, `high CPU`, `slow query` → **performance + analyzer**
- `SQL injection`, `XSS`, `CSRF` → **security + analyzer**
Suggestion Patterns
Single Role Suggestion
$ /smart-review src/auth/login.js
→ "Authentication file detected"
→ "Analysis with security role recommended"
→ "Execute? [y]es / [n]o / [m]ore options"
Multiple Role Suggestion
$ /smart-review src/mobile/components/
→ "📱🎨 Mobile + Frontend elements detected"
→ "Recommended approaches:"
→ "[1] mobile role alone"
→ "[2] frontend role alone"
→ "[3] multi-role mobile,frontend"
→ "[4] role-debate mobile,frontend"
Suggestions for Problem Analysis
$ /smart-review error.log
→ "⚠️ Error log detected"
→ "Starting root cause analysis with analyzer role"
→ "[Auto-execute] /role analyzer"
$ /smart-review slow-api.log
→ "🐌 Performance issue detected"
→ "Recommended: [1]/role performance [2]/role-debate performance,analyzer"
Suggestions for Complex Design Decisions
$ /smart-review architecture-design.md
→ "🏗️🔒⚡ Architecture + Security + Performance elements detected"
→ "For complex design decisions, debate format recommended"
→ "[Recommended] /role-debate architect,security,performance"
→ "[Alternative] /multi-role architect,security,performance"
Suggestion Logic Details
Priority Assessment
1. **Security** - Authentication, authorization, and encryption are top priorities 2. **Critical Errors** - System outages and data loss are urgent 3. **Architecture** - Large-scale changes and technology selection require careful consideration 4. **Performance** - Directly impacts user experience 5. **Frontend/Mobile** - UI/UX improvements 6. **QA** - Quality assurance and testing
Conditions for Recommending Debate
- When 3 or more roles are involved
- When there's a trade-off between security and performance
- When significant architectural changes are involved
- When both mobile and web are affected
Basic Examples
# Analyze current directory
/smart-review
"Suggest the optimal role and approach"
# Analyze specific file
/smart-review src/auth/login.js
"Suggest the best review method for this file"
# Analyze error log
/smart-review error.log
"Suggest the best approach to resolve this error"
Practical Examples
Project-wide Analysis
$ /smart-review
→ "📊 Analyzing project..."
→ "React + TypeScript project detected"
→ "Authentication functionality + API + mobile support confirmed"
→ ""
→ "💡 Recommended workflow:"
→ "1. Check authentication with security"
→ "2. Evaluate UI/UX with frontend"
→ "3. Confirm mobile optimization with mobile"
→ "4. Review overall design with architect"
→ ""
→ "Auto-execute? [y]es / [s]elect role / [c]ustom"
Specific Problem Analysis
$ /smart-review "How to set JWT expiration time"
→ "🤔 Technical design decision detected"
→ "This issue requires multiple expert perspectives"
→ ""
→ "Recommended approach:"
→ "/role-debate security,performance,frontend"
→ "Reason: Balance between security, performance, and UX is important"
Collaboration with Claude
# Analysis combined with file content
cat src/auth/middleware.js
/smart-review
"Analyze this file from a security perspective"
# Analysis combined with errors
npm run build 2>&1 | tee build-error.log
/smart-review build-error.log
"Suggest ways to resolve build errors"
# Design consultation
/smart-review
"Discuss whether to choose React Native or Progressive Web App"
Notes
- Suggestions are for reference only. The final decision is up to the user
- Debate format (role-debate) is recommended for complex issues
- Single role is often sufficient for simple problems
- Security-related matters should always be confirmed with a specialized role
Read more
description: 'Auto-suggest optimal role and approach. Trigger with "review this", "check code quality", "best approach?", "how to improve?".' allowed-tools: - Read - Grep - Glob
Auto-suggest optimal role and approach
A command that analyzes the current situation and automatically suggests the optimal role and approach.
Usage
/smart-review # Analyze current directory /smart-review <file/directory> # Analyze specific target
Automatic Analysis Logic
Analysis by File Extension
- `package.json`, `*.tsx`, `*.jsx`, `*.css`, `*.scss` → **frontend**
- `Dockerfile`, `docker-compose.yml`, `*.yaml` → **architect**
- `*.test.js`, `*.spec.ts`, `test/`, `__tests__/` → **qa**
- `*.rs`, `Cargo.toml`, `performance/` → **performance**
Security-related File Detection
- `auth.js`, `security.yml`, `.env`, `config/auth/` → **security**
- `login.tsx`, `signup.js`, `jwt.js` → **security + frontend**
- `api/auth/`, `middleware/auth/` → **security + architect**
Complex Analysis Patterns
- `mobile/` + `*.swift`, `*.kt`, `react-native/` → **mobile**
- `webpack.config.js`, `vite.config.js`, `large-dataset/` → **performance**
- `components/` + `responsive.css` → **frontend + mobile**
- `api/` + `auth/` → **security + architect**
Error/Problem Analysis
- Stack traces, `error.log`, `crash.log` → **analyzer**
- `memory leak`, `high CPU`, `slow query` → **performance + analyzer**
- `SQL injection`, `XSS`, `CSRF` → **security + analyzer**
Suggestion Patterns
Single Role Suggestion
$ /smart-review src/auth/login.js → "Authentication file detected" → "Analysis with security role recommended" → "Execute? [y]es / [n]o / [m]ore options"
Multiple Role Suggestion
$ /smart-review src/mobile/components/ → "📱🎨 Mobile + Frontend elements detected" → "Recommended approaches:" → "[1] mobile role alone" → "[2] frontend role alone" → "[3] multi-role mobile,frontend" → "[4] role-debate mobile,frontend"
Suggestions for Problem Analysis
$ /smart-review error.log → "⚠️ Error log detected" → "Starting root cause analysis with analyzer role" → "[Auto-execute] /role analyzer" $ /smart-review slow-api.log → "🐌 Performance issue detected" → "Recommended: [1]/role performance [2]/role-debate performance,analyzer"
Suggestions for Complex Design Decisions
$ /smart-review architecture-design.md → "🏗️🔒⚡ Architecture + Security + Performance elements detected" → "For complex design decisions, debate format recommended" → "[Recommended] /role-debate architect,security,performance" → "[Alternative] /multi-role architect,security,performance"
Suggestion Logic Details
Priority Assessment
1. **Security** - Authentication, authorization, and encryption are top priorities 2. **Critical Errors** - System outages and data loss are urgent 3. **Architecture** - Large-scale changes and technology selection require careful consideration 4. **Performance** - Directly impacts user experience 5. **Frontend/Mobile** - UI/UX improvements 6. **QA** - Quality assurance and testing
Conditions for Recommending Debate
- When 3 or more roles are involved
- When there's a trade-off between security and performance
- When significant architectural changes are involved
- When both mobile and web are affected
Basic Examples
# Analyze current directory /smart-review "Suggest the optimal role and approach" # Analyze specific file /smart-review src/auth/login.js "Suggest the best review method for this file" # Analyze error log /smart-review error.log "Suggest the best approach to resolve this error"
Practical Examples
Project-wide Analysis
$ /smart-review → "📊 Analyzing project..." → "React + TypeScript project detected" → "Authentication functionality + API + mobile support confirmed" → "" → "💡 Recommended workflow:" → "1. Check authentication with security" → "2. Evaluate UI/UX with frontend" → "3. Confirm mobile optimization with mobile" → "4. Review overall design with architect" → "" → "Auto-execute? [y]es / [s]elect role / [c]ustom"
Specific Problem Analysis
$ /smart-review "How to set JWT expiration time" → "🤔 Technical design decision detected" → "This issue requires multiple expert perspectives" → "" → "Recommended approach:" → "/role-debate security,performance,frontend" → "Reason: Balance between security, performance, and UX is important"
Collaboration with Claude
# Analysis combined with file content cat src/auth/middleware.js /smart-review "Analyze this file from a security perspective" # Analysis combined with errors npm run build 2>&1 | tee build-error.log /smart-review build-error.log "Suggest ways to resolve build errors" # Design consultation /smart-review "Discuss whether to choose React Native or Progressive Web App"
Notes
- Suggestions are for reference only. The final decision is up to the user
- Debate format (role-debate) is recommended for complex issues
- Single role is often sufficient for simple problems
- Security-related matters should always be confirmed with a specialized role
A collection of commands, roles, and automation scripts for Claude Code. Automate your workflow without unnecessary confirmations, allowing you to focus on what matters.
Repo: wasabeef/claude-code-cookbook
Other skills on claude-code-cookbook.
- /analyze-dependencies
Analyze project dependencies and evaluate architectural health. Trigger with "analyze dependencies", "detect circular dependencies", "architecture issues?", "check module coupling", "find layer violations". Generates dependency matrix, fan-in/fan-out analysis, and prioritized
Open skill - /analyze-performance
Performance analysis based on Core Web Vitals with UX scoring. Trigger with "analyze performance", "improve speed", "check Core Web Vitals", "page speed", "improve LCP", "identify performance issues".
Open skill - /check-fact
Verify information accuracy against codebase and documentation. Trigger with "is this correct?", "fact check", "verify this", "is this accurate?".
Open skill - /check-prompt
Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".
Open skill - /commit-message
Generate commit messages from staged changes. Trigger with "suggest commit message", "generate commit message", "what should the commit say?", "write commit message".
Open skill - /context7
Search technical documentation via Context7 MCP. Trigger with "check the docs", "look up documentation", "how to use this library?", "API reference".
Open skill

