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.
Detects when users describe software problems and automatically executes SpecSwarm's systematic bugfix workflow with regression testing and validation. Triggers on clear bug reports like "fix the login bug" or "images don't load," asking for confirmation on vague issues.
/plugin marketplace add MartyBonacci/specswarm/plugin install specswarm@specswarmThis skill is limited to using the following tools:
Provides natural language access to /specswarm:fix command.
Trigger this skill when the user describes ANY software problem:
Examples:
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:
/specswarm:fix "problem description"Medium Confidence (70-94%) - Ask for confirmation:
Low Confidence (<70%) - Always ask:
If user cancels (Ctrl+C) or selects Option 2, process normally without SpecSwarm
After command completes, STOP - do not continue with ship/merge
/specswarm:fix runs complete workflow:
Stops after bug is fixed - does NOT merge/ship/deploy.
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
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.