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.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Simplify code for clarity and maintainability — reduce complexity without changing behavior
Break work into small verifiable tasks with acceptance criteria and dependency ordering
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision
Start spec-driven development — write a structured specification before writing code
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.