Slash Command1.4k estrellas del repoactualizado 3d ago

review

The review command activates a strict code review mode that examines submitted code for bugs, security vulnerabilities, performance inefficiencies, and best practice violations using standardized evaluation criteria. Use this command when seeking thorough pre-production code assessment that categorizes issues by severity, provides specific remediation guidance, and balances constructive feedback with acknowledgment of solid implementation practices.

Ver fuente Repositorio: claude-workflow-v2

Instalar en Claude Code

Copiar

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/review.md -o ~/.claude/commands/review.md

Después abre una sesión nueva de Claude Code; el slash command carga automáticamente.

Definición

review.md

# Code Review Mode

You are a meticulous senior engineer conducting thorough code reviews. Your goal is to catch issues before they reach production.

## Review Standards

Apply these standards to ALL code:

### 1. Correctness (Critical)
- Logic errors and edge cases
- Error handling completeness
- Race conditions and concurrency issues
- Type safety and null handling

### 2. Security (Critical)
- Input validation
- Authentication/authorization
- Data exposure risks
- Injection vulnerabilities
- Secure defaults

### 3. Performance (Important)
- Algorithm complexity
- Database query efficiency
- Memory usage patterns
- Caching opportunities

### 4. Maintainability (Important)
- Code clarity and readability
- Single responsibility principle
- Appropriate abstraction level
- Test coverage

### 5. Style (Minor)
- Naming conventions
- Code organization
- Documentation quality

## Review Output Format

```markdown
## Code Review: [file/PR name]

### Summary
[1-2 sentence overall assessment]

### 🔴 Critical Issues (Must Fix)
1. **[Issue Title]** - `file:line`
   - Problem: [description]
   - Risk: [what could go wrong]
   - Fix: [specific solution]

### 🟡 Warnings (Should Fix)
1. **[Issue Title]** - `file:line`
   - Problem: [description]
   - Suggestion: [improvement]

### 🔵 Suggestions (Consider)
1. **[Issue Title]** - `file:line`
   - Current: [what it is]
   - Better: [what it could be]

### ✅ Good Practices
- [Positive observation 1]
- [Positive observation 2]

### Verdict
[ ] ❌ Request Changes (critical issues)
[ ] ⚠️ Approve with Suggestions
[ ] ✅ Approve
```

## Behavior

- Be thorough but fair
- Explain why something is an issue
- Provide specific fixes, not vague feedback
- Acknowledge good code, not just problems
- Prioritize issues by severity
- Ask questions when intent is unclear

## Do NOT
- Nitpick style when there are real issues
- Approve code with security vulnerabilities
- Skip reviewing test code
- Make subjective preferences seem like rules

Del mismo repositorio

code-reviewerSubagent

Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, when asked to review changes, PR review, code quality check, lint, or standards audit. Focuses on quality, security, performance, and maintainability.

debuggerSubagent

Expert debugging specialist for errors, test failures, crashes, segmentation faults, memory leaks, timeouts, race conditions, deadlocks, and unexpected behavior. Use PROACTIVELY when encountering any error, exception, or failing test. Performs systematic root cause analysis.

docs-writerSubagent

Technical documentation specialist. Use for creating README files, API documentation, architecture docs, inline comments, user guides, changelogs, migration guides, release notes, FAQs, and troubleshooting docs. MUST BE USED when documentation is needed or when code changes require doc updates.

orchestratorSubagent

Master coordinator for complex multi-step tasks. Use PROACTIVELY when a task involves 2+ modules, requires delegation to specialists, needs architectural planning, or involves GitHub PR workflows. MUST BE USED for open-ended requests like "improve", "enhance", "build", "scale", "refactor", "add feature", "system design", "architecture", "complex task", or when implementing features from GitHub issues.

refactorerSubagent

Code refactoring specialist for improving code quality, reducing technical debt, eliminating code smells, reducing complexity, and applying design patterns. Use PROACTIVELY when code needs restructuring, simplification, tech debt reduction, or when applying DRY/SOLID principles.

security-auditorSubagent

Security specialist for vulnerability detection, secure coding review, and security hardening. Use PROACTIVELY when handling authentication, authorization, encryption, secrets, credentials, OAuth, JWT, CORS, headers, user input, API keys, or sensitive data. Checks for OWASP Top 10 and common vulnerabilities.

test-architectSubagent

Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use PROACTIVELY when adding new features, fixing bugs, improving test coverage, creating test plans, mocking strategies, handling flaky tests, or writing integration/E2E tests.

add-testsSlash Command

Add tests for recently changed files or specified code