fixing

Fixing

Unified skill for fixing issues of any complexity with intelligent routing.

Step 0: Mode Selection

First action: If there is no "auto" keyword in the request, use AskUserQuestion to determine workflow mode:

See references/mode-selection.md for AskUserQuestion format.

Step 1: Complexity Assessment

Classify before routing. See references/complexity-assessment.md.

Skill/Subagent Activation Matrix

See references/skill-activation-matrix.md for complete matrix.

Always activate: debugging (all workflows) Conditional: problem-solving, sequential-thinking, brainstorming, context-engineering Subagents: debugger, researcher, planner, code-reviewer, tester, Bash Parallel: Multiple Explore agents for scouting, Bash agents for verification

Output Format

Unified step markers:

✓ Step 0: [Mode] selected - [Complexity] detected
✓ Step 1: Root cause identified - [summary]
✓ Step 2: Fix implemented - [N] files changed
✓ Step 3: Tests [X/X passed]
✓ Step 4: Review [score]/10 - [status]
✓ Step 5: Complete - [action taken]

References

Load as needed:

• references/mode-selection.md - AskUserQuestion format for mode
• references/complexity-assessment.md - Classification criteria
• references/workflow-quick.md - Quick: debug → fix → review
• references/workflow-standard.md - Standard: full pipeline
• references/workflow-deep.md - Deep: research + brainstorm + plan
• references/review-cycle.md - Review logic (autonomous vs HITL)
• references/skill-activation-matrix.md - When to activate each skill
• references/parallel-exploration.md - Parallel Explore/Bash subagents patterns

Specialized Workflows:

• references/workflow-ci.md - GitHub Actions/CI failures
• references/workflow-logs.md - Application log analysis
• references/workflow-test.md - Test suite failures
• references/workflow-types.md - TypeScript type errors
• references/workflow-ui.md - Visual/UI issues (requires design skills)