Intelligent routing to the right fix strategy

Quick Start

/fix TypeScript compilation errors in campaign module

What happens:

  1. Analyzes issue type (type errors detected)
  2. Routes to type fixer (auto-detected)
  3. Specialized agent fixes issues
  4. Verifies with type checker

Syntax

/fix [issues]

Decision Tree

The /fix command intelligently routes to specialized variants:

Issue TypeKeywordsRoutes ToAgent
Type Errorstype, typescript, tsc/fix (auto-detect types)type-fixer
UI/UXui, ux, design, layout, style/fix (auto-detect UI)ui-ux-designer
CI/CDgithub actions, pipeline, workflow/fix (auto-detect CI)devops-specialist
Teststest, spec, jest, vitest/fix (auto-detect test)tester
Logslogs, error logs, stack trace/fix (auto-detect logs)debugger
Multiple2+ unrelated issues/fix --parallelmultiple agents
Complexarchitecture, refactor, system-wide/fix (auto-detect complexity)architect
Simplesingle file, small bug/fix --quickgeneralist

Examples

Example 1: Type Errors

Input:

/fix TypeScript compilation errors

Routes to: /fix (auto-detects type errors)

Output:

✓ Analyzed: 14 type errors in 6 files
✓ Fixed: All 14 errors resolved
✓ Verified: tsc passes with 0 errors

Fixed files:
- lib/campaign/manager.ts (3 errors)
- lib/email/sender.ts (5 errors)
- components/CampaignCard.tsx (4 errors)
- types/campaign.ts (2 errors)

Total time: 47 seconds

Example 2: UI Issues

Input:

/fix Button not responsive on mobile devices

Routes to: /fix (auto-detects UI context)

Output:

✓ ui-ux-designer: Issue analyzed
✓ Fixed: Mobile responsiveness added
✓ Verified: Tested on viewport 375px-768px

Changes:
- Added responsive classes to Button component
- Fixed padding on mobile (<640px)
- Adjusted font size for small screens
- Tested touch targets (min 44x44px)

Files modified: components/Button.tsx

Example 3: CI/CD Failures

Input:

/fix GitHub Actions deployment pipeline failing

Routes to: /fix (auto-detects CI context)

Output:

✓ Pipeline analyzed: Build stage failing
✓ Root cause: Node version mismatch
✓ Fixed: Updated workflow to Node 20
✓ Verified: Build passes

Changes:
- Updated .github/workflows/deploy.yml (Node 18 → 20)
- Removed deprecated npm commands
- Added caching for node_modules

Re-run pipeline: Build now passes ✓

Example 4: Multiple Issues

Input:

/fix Type errors in auth module + UI bugs in dashboard + test failures

Routes to: /fix --parallel

Output:

✓ Spawned 3 agents in parallel:
   - Agent 1: Type errors (fix:types)
   - Agent 2: UI bugs (fix:ui)
   - Agent 3: Test failures (fix:test)

Results (parallel execution, 2min 15sec):
✓ Agent 1: 8 type errors fixed (auto-detected)
✓ Agent 2: 3 UI bugs resolved (auto-detected)
✓ Agent 3: 5 tests now passing (auto-detected)

Total time: 2m 15s (vs 6m 45s sequential)
Time saved: 67%

Variants

/fix —quick

Quick fixes for simple issues:

/fix --quick Missing semicolon in utils.ts

/fix (complex)

Deep architectural fixes (auto-detects complexity):

/fix Refactor campaign architecture for scalability

/fix —parallel

Multiple unrelated issues:

/fix --parallel Fix types + UI bugs + test failures

/fix (type errors)

TypeScript type errors (auto-detected):

/fix

/fix (UI issues)

UI/UX issues (auto-detected from context):

/fix [description]

/fix (CI/CD)

CI/CD pipeline failures (auto-detected from context):

/fix [github-actions-url]

/fix (test failures)

Test failures (auto-detected from context):

/fix [description]

/fix (logs)

Analyze error logs (auto-detected from context):

/fix [description]

Workflow Integration

# After /cook if issues arise
/cook plans/feature.md
# Tests fail or types error
/fix TypeScript errors + failing tests

# After /analyze identifies issues
/analyze campaigns
/fix Campaign analytics not tracking conversions

# Quick iteration
/cook add feature
# Minor issues
/fix --quick Issues from last commit
  • /cook - Implementation (includes testing)
  • /test - Run tests only
  • /review - Code quality check
  • /debug - Deep root cause analysis

Fix smart. Not hard. Intelligent routing to the right solution strategy.