| name | fix |
| description | ALWAYS activate this skill before fixing ANY bug, error, test failure, CI/CD issue, type error, lint, log error, UI issue, code problem. |
| version | 1.1.0 |
Fixing
Unified skill for fixing issues of any complexity with intelligent routing.
Arguments
--auto - Activate autonomous mode (default)--review - Activate human-in-the-loop review mode--quick - Activate quick mode
Workflow
Step 1: Mode Selection
First action: If there is no "auto" keyword in the request, use AskUserQuestion to determine workflow mode:
| Option | Recommend When | Behavior |
|---|
| Autonomous (default) | Simple/moderate issues | Auto-approve if score >= 9.5 & 0 critical |
| Human-in-the-loop Review | Critical/production code | Pause for approval at each step |
| Quick | Type errors, lint, trivial bugs | Fast debug → fix → review cycle |
See references/mode-selection.md for AskUserQuestion format.
Step 2: Debug
- Activate
debug skill.
- Guess all possible root causes.
- Spawn multiple
Explore subagents in parallel to verify each hypothesis.
- Create report with all findings for the next step.
Step 3: Complexity Assessment & Fix Implementation
Classify before routing. See references/complexity-assessment.md.
| Level | Indicators | Workflow |
|---|
| Simple | Single file, clear error, type/lint | references/workflow-quick.md |
| Moderate | Multi-file, root cause unclear | references/workflow-standard.md |
| Complex | System-wide, architecture impact | references/workflow-deep.md |
| Parallel | 2+ independent issues | Parallel fullstack-developer agents |
Step 4: Fix Verification & Prevent Future Issues
- Read and analyze all the implemented changes.
- Spawn multiple
Explore subagents to find possible related code for verification.
- Make sure these fixes don't break other parts of the codebase.
- Prevent future issues by adding comprehensive validation.
Step 5: Finalize
- Report summary to user with confidence level/score, all the changes and related files.
- Ask to commit via
git-manager subagent and update docs if needed via docs-manager subagent (in parallel).
IMPORTANT: Skill/Subagent Activation Matrix
See references/skill-activation-matrix.md for complete matrix.
Always activate: debug (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 modereferences/complexity-assessment.md - Classification criteriareferences/workflow-quick.md - Quick: debug → fix → reviewreferences/workflow-standard.md - Standard: full pipelinereferences/workflow-deep.md - Deep: research + brainstorm + planreferences/review-cycle.md - Review logic (autonomous vs HITL)references/skill-activation-matrix.md - When to activate each skillreferences/parallel-exploration.md - Parallel Explore/Bash subagents patterns
Specialized Workflows:
references/workflow-ci.md - GitHub Actions/CI failuresreferences/workflow-logs.md - Application log analysisreferences/workflow-test.md - Test suite failuresreferences/workflow-types.md - TypeScript type errorsreferences/workflow-ui.md - Visual/UI issues (requires design skills)
