architect
Analyze codebase architecture, classify dependencies, detect patterns and anti-patterns, and generate Architecture Decision Records. TRIGGER when: user asks about architecture, dependency analysis, ADRs, coupling, or wants to understand how a codebase is structured. DO NOT TRIGGER when: user wants a code review of specific files (use code-review), or wants to fix a bug (use focused-fix).
Repository SourceNeeds Review
code-review
Structured code review with blast radius analysis, security scanning, quality scoring, and a 30+ item checklist.
TRIGGER when: user asks to review a PR, diff, changeset, or code for quality/security/breaking changes; user runs /review or /code-review; reviewing staged or committed changes.
DO NOT TRIGGER when: writing new code from scratch, refactoring without review context, general debugging.
Repository SourceNeeds Review
focused-fix
Structured 5-phase bug fix methodology with root cause verification. TRIGGER when: user wants to fix a bug, debug an issue, investigate a failure, or says "focused fix". Also when a fix attempt has failed and the user wants a systematic approach. DO NOT TRIGGER when: user wants architecture analysis (use architect), QA triage (use qa), or code review (use code-review).
Repository SourceNeeds Review
performance-profiler
Profiling and optimization across languages in the polyglot stack. TRIGGER when: user asks about performance profiling, flamegraphs, benchmarks, load testing, memory leaks, or optimizing slow code paths in Node.js, Python, Go, Elixir, or Rust. DO NOT TRIGGER when: database-specific optimization (use database-designer), or build/bundle size issues without runtime perf concern.
Repository SourceNeeds Review