review
The `/review` command performs a comprehensive code review of staged or recent commits across five dimensions: correctness against specifications and edge cases, readability of naming and logic, architectural alignment with existing patterns, security practices including input validation and authentication, and performance considerations like query optimization. Use this command when submitting code changes to identify defects, maintainability issues, and risks before merging.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/addyosmani/agent-skills/HEAD/.claude/commands/review.md -o ~/.claude/commands/review.mdreview.md
Invoke the agent-skills:code-review-and-quality skill. Review the current changes (staged or recent commits) across all five axes: 1. **Correctness** — Does it match the spec? Edge cases handled? Tests adequate? 2. **Readability** — Clear names? Straightforward logic? Well-organized? 3. **Architecture** — Follows existing patterns? Clean boundaries? Right abstraction level? 4. **Security** — Input validated? Secrets safe? Auth checked? (Use security-and-hardening skill) 5. **Performance** — No N+1 queries? No unbounded ops? (Use performance-optimization skill) Categorize findings as Critical, Important, or Suggestion. Output a structured review with specific file:line references and fix recommendations.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Simplify code for clarity and maintainability — reduce complexity without changing behavior