code-review-expert
Comprehensive code review expertise. Use when reviewing code, evaluating architecture, or assessing quality. Triggers on review, evaluate, assess, audit, code quality, best practices.
When & Why to Use This Skill
The Code Review Expert skill provides a comprehensive, multi-layered analysis of software codebases to ensure high quality, robust architecture, and security compliance. By following a structured five-step workflow—from initial structural scans to deep-dive security audits—it helps development teams identify critical bugs, performance bottlenecks, and deviations from industry best practices before deployment.
Use Cases
- Pre-merge Pull Request Reviews: Automatically evaluate code changes for logic errors, type safety (e.g., avoiding 'any' types), and proper error handling before merging into the main branch.
- Architectural Integrity Assessment: Analyze the relationship between modules and functions to ensure the system design remains scalable, modular, and follows established patterns.
- Security and Vulnerability Auditing: Perform deep-dive inspections to detect hardcoded secrets, missing input validation, and insecure database queries (e.g., ensuring parameterized queries).
- Technical Debt and Quality Benchmarking: Use a standardized severity scale (Critical to Low) to prioritize refactoring tasks and maintain long-term code health.
- Cross-Functional Perspective Analysis: Review code from the viewpoints of different stakeholders, including QA for testability, UX for performance impact, and DevOps for deployment readiness.
| name | code-review-expert |
|---|---|
| description | Comprehensive code review expertise. Use when reviewing code, evaluating architecture, or assessing quality. Triggers on review, evaluate, assess, audit, code quality, best practices. |
Code Review Expert
Comprehensive code review expertise for evaluating architecture and quality.
When to Use
- Reviewing code changes before merge
- Evaluating architecture decisions
- Assessing code quality
- Auditing for security issues
- Performing pre-commit reviews
Workflow
Step 1: Initial Scan (10%)
Review structure and architecture overview.
Step 2: Top-Down Review (40%)
Architecture → Modules → Functions.
Step 3: Multi-Perspective (30%)
Review as Architect, PM, QA, UX.
Step 4: Deep Dives (15%)
Focus on security and performance.
Step 5: Report (5%)
Summarize and prioritize findings.
Review Phases
Phase 1 (10%): Initial scan - structure, architecture
Phase 2 (40%): Top-down - Architecture → Modules → Functions
Phase 3 (30%): Multi-perspective - Architect, PM, QA, UX
Phase 4 (15%): Deep dives - Security, performance
Phase 5 (5%): Report - Summarize, prioritize
Severity
| Level | Action |
|---|---|
| 🔴 Critical | Must fix before deploy |
| 🟠 High | Fix this sprint |
| 🟡 Medium | Fix next sprint |
| 🟢 Low | Backlog |
Quick Checklist
- No
anytypes - Error handling complete
- Input validation present
- No hardcoded secrets
- Parameterized queries
- Async errors handled