build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Conduct a five-axis code review — correctness, readability, architecture, security, performance
> /plugin marketplace add addyosmani/agent-skills > /plugin install agent-skills@addy-agent-skills
How it fires
How this command gets triggered: by you, by Claude, or both.
/reviewContext preview
What this command does when you run it.
Conduct a five-axis code review — correctness, readability, architecture, security, performance
description: Conduct a five-axis code review — correctness, readability, architecture, security, performance
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.
Production-grade engineering skills for AI coding agents. Skills encode the workflows, quality gates, and best practices that senior engineers use when building software.
Get the whole plugin, auto-invokedRepo: addyosmani/agent-skills
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
Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md
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