one-for-all

Implement the next task incrementally — build, test, verify, commit

Simplify code for clarity and maintainability — reduce complexity without changing behavior

Break work into small verifiable tasks with acceptance criteria and dependency ordering

Conduct a five-axis code review — correctness, readability, architecture, security, performance

Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision

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.

QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

Designs stable, hard-to-misuse APIs and module interfaces — contract first, validation at the boundary, additive evolution, consistent error semantics. Use when designing new REST or GraphQL endpoints, defining type contracts between modules or teams, creating component prop interfaces, or changing any *public* interface. Triggers on phrases like "design this API", "what should the contract look like", "let's define the interface", or any change that adds/modifies an endpoint or exported type. Skip for purely internal helpers with one caller, code refactors that don't alter the public surface, and changes confined to a single module's private functions — interface-design discipline is for *contracts*, not for every function call.

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.

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.

Multi-dimensional code review with quality gates. Every change gets reviewed before merge — no exceptions. Review covers five axes: correctness, readability, architecture, security, and performance.

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.

1 hook across 1 event