SpecSwarm Fix Workflow
Provides natural language access to /specswarm:fix command.
When to Invoke
Trigger this skill when the user describes ANY software problem:
- Things not working or broken
- Errors, bugs, or failures
- Features not loading or functioning
- Requests to fix, debug, or resolve issues
- ANY report of unexpected behavior
Examples:
- "Please fix that the images don't load"
- "Images don't load"
- "Fix the login bug"
- "The checkout is broken"
- "There's an error when submitting forms"
- "Authentication doesn't work"
- "Payment processing fails"
- "The search isn't working"
Instructions
Confidence-Based Execution:
Detect that user described a software problem
Extract the problem description from their message
Assess confidence and execute accordingly:
High Confidence (95%+) - Auto-execute immediately:
- Clear bug descriptions: "fix the login bug", "images don't load", "checkout is broken"
- Action: Immediately run
/specswarm:fix "problem description"
- Show brief notification: "🎯 Running /specswarm:fix... (press Ctrl+C within 3s to cancel)"
Medium Confidence (70-94%) - Ask for confirmation:
- Less specific: "something's wrong with authentication", "the app has issues"
- Action: Use AskUserQuestion tool with two options:
- Option 1 (label: "Run /specswarm:fix"): Use SpecSwarm's systematic bugfix workflow
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
Low Confidence (<70%) - Always ask:
- Vague: "the app isn't working right", "there's a problem"
- Action: Use AskUserQuestion as above
If user cancels (Ctrl+C) or selects Option 2, process normally without SpecSwarm
After command completes, STOP - do not continue with ship/merge
What the Fix Command Does
/specswarm:fix runs complete workflow:
- Creates regression tests to reproduce bug
- Implements the fix
- Verifies fix works
- Re-runs tests to catch new failures
- Auto-retries up to 2 times if needed
Stops after bug is fixed - does NOT merge/ship/deploy.
Semantic Understanding
This skill should trigger not just on exact keywords, but semantic equivalents:
Fix equivalents: fix, repair, resolve, debug, correct, address, handle, patch
Broken equivalents: broken, not working, doesn't work, not showing, not appearing, not displaying, not rendering, not loading, failing, crashed
Issue terms: bug, error, problem, issue, trouble, failure
1---2name: specswarm-fix3description: Systematic bugfix workflow with regression testing, auto-retry logic, and comprehensive validation. Auto-executes when user clearly wants to fix, debug, repair, resolve, broken, not working, doesn't work, not showing up, not appearing, not displaying, not rendering, doesn't show, won't show, isn't showing, doesn't appear, doesn't display, failing, errors, bugs, issues, not loading, doesn't load, crashed, crashes, problem with, trouble with.4---5
6# SpecSwarm Fix Workflow
7
8Provides natural language access to `/specswarm:fix` command.
9
10## When to Invoke
11
12Trigger this skill when the user describes ANY software problem:
13- Things not working or broken
14- Errors, bugs, or failures
15- Features not loading or functioning
16- Requests to fix, debug, or resolve issues
17- ANY report of unexpected behavior
18
19**Examples:**
20- "Please fix that the images don't load"
21- "Images don't load"
22- "Fix the login bug"
23- "The checkout is broken"
24- "There's an error when submitting forms"
25- "Authentication doesn't work"
26- "Payment processing fails"
27- "The search isn't working"
28
29## Instructions
30
31**Confidence-Based Execution:**
32
331. **Detect** that user described a software problem
342. **Extract** the problem description from their message
353. **Assess confidence and execute accordingly**:
36
37 **High Confidence (95%+)** - Auto-execute immediately:
38 - Clear bug descriptions: "fix the login bug", "images don't load", "checkout is broken"
39 - Action: Immediately run `/specswarm:fix "problem description"`
40 - Show brief notification: "🎯 Running /specswarm:fix... (press Ctrl+C within 3s to cancel)"
41
42 **Medium Confidence (70-94%)** - Ask for confirmation:
43 - Less specific: "something's wrong with authentication", "the app has issues"
44 - Action: Use AskUserQuestion tool with two options:
45 - Option 1 (label: "Run /specswarm:fix"): Use SpecSwarm's systematic bugfix workflow
46 - Option 2 (label: "Process normally"): Handle as regular Claude Code request
47
48 **Low Confidence (<70%)** - Always ask:
49 - Vague: "the app isn't working right", "there's a problem"
50 - Action: Use AskUserQuestion as above
51
524. **If user cancels (Ctrl+C) or selects Option 2**, process normally without SpecSwarm
535. **After command completes**, STOP - do not continue with ship/merge
54
55## What the Fix Command Does
56
57`/specswarm:fix` runs complete workflow:
58- Creates regression tests to reproduce bug
59- Implements the fix
60- Verifies fix works
61- Re-runs tests to catch new failures
62- Auto-retries up to 2 times if needed
63
64Stops after bug is fixed - does NOT merge/ship/deploy.
65
66## Semantic Understanding
67
68This skill should trigger not just on exact keywords, but semantic equivalents:
69
70**Fix equivalents**: fix, repair, resolve, debug, correct, address, handle, patch
71**Broken equivalents**: broken, not working, doesn't work, not showing, not appearing, not displaying, not rendering, not loading, failing, crashed
72**Issue terms**: bug, error, problem, issue, trouble, failure
majiayu000