code-review
Systematic multi-perspective code review with consistent quality gates.
When & Why to Use This Skill
The Code Review skill provides a systematic, multi-perspective approach to software quality assurance. By implementing consistent quality gates, it moves beyond superficial checks to perform rigorous security, performance, and architectural reviews, ensuring codebases remain robust, efficient, and maintainable through automated verification workflows.
Use Cases
- Automated Self-Review: Perform a rigorous check of your own code against established quality gates before submitting pull requests to reduce review cycles.
- Multi-Pass Security Auditing: Conduct dedicated security reviews focusing on authentication, Row Level Security (RLS), and input validation to prevent vulnerabilities.
- Performance Bottleneck Identification: Analyze code for database inefficiencies and UI re-render issues to maintain high application performance.
- Architectural Alignment: Verify that implementation plans and code changes adhere to defined state management and data flow patterns.
- Standardized Peer Reviews: Assist human reviewers or other AI agents by providing consistent checklists and procedures for PR evaluations.
| name | code-review |
|---|---|
| description | Systematic multi-perspective code review with consistent quality gates. |
| last_updated | 2025-12-20 |
Code Review Skill
Overview
A systematic approach to code review that moves beyond "it looks good" to rigorous quality verification. This skill provides specific checklists and procedures for different review types.
When To Use
- Self-Review: Before submitting a PR or finishing
/work - Peer Review: When reviewing another agent's or human's code (
/resolve_pr) - Plan Review: When validating an implementation plan (
/plan_review)
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "code-review" "manual" "$$"
What do you want to do?
- Security Review (Auth, RLS, Input) →
workflows/security-pass.md - Performance Review (Database, Re-renders) →
workflows/performance-pass.md - Architecture Review (State, Data Flow) →
workflows/architecture-pass.md - General Quality Check →
checklists/pre-merge.md
Key Principles
- Review in Passes: Don't check everything at once. Do a security pass, then a performance pass, etc.
- Reference Patterns: Always check against
docs/solutions/patterns/critical-patterns.md. - Verify, Don't Guess: If you see a potential issue, verify it with a quick test or script.