/devkit.fix-debugging

description: Provides guided bug fixing and debugging capability with systematic root cause analysis. Use when encountering bugs, errors, or unexpected behavior.
argument-hint: "[ --lang=java|spring|typescript|nestjs|react|python|general ] [ issue-description or error-message ]"
allowed-tools: Task, Read, Write, Edit, Bash, Grep, Glob, TodoWrite, AskUserQuestion
model: inherit

Fix & Debugging

Overview

You are helping a developer fix a bug or debug an issue. Follow a systematic approach: understand the problem, trace the root cause, design a minimal fix, then implement and verify.

Usage

/developer-kit:devkit.fix-debugging [--lang=java|spring|typescript|nestjs|react|python|general] [issue-description or error-message]

Arguments

| Argument | Description | |----------|-------------| | `$ARGUMENTS` | Combined arguments passed to the command |

Current Context

The command will automatically gather context information when needed:

• Current git branch and status
• Recent commits and changes
• Available when the repository has history

Execution Instructions

**Agent Selection**: Based on the `--lang` parameter, select the appropriate agents:

Integration with Sub-agents

This command leverages specialized sub-agents using the Task tool.

Language/Framework Selection

Parse $ARGUMENTS to detect the optional `--lang` parameter:

• `--lang=spring` or `--lang=java`: Use Java/Spring Boot specialized agents
• `--lang=typescript` or `--lang=ts`: Use TypeScript specialized agents
• `--lang=nestjs`: Use NestJS specialized agents
• `--lang=react`: Use React frontend specialized agents
• `--lang=aws`: Use AWS specialized agents (architecture, CloudFormation, IaC)
• `--lang=python` or `--lang=py`: Use Python specialized agents
• `--lang=general` or no flag: Use general-purpose agents (default)

**Agent Mapping by Language:**

| Phase | General (default) | Java/Spring Boot (`--lang=spring` or `--lang=java`) | TypeScript (`--lang=typescript` or `--lang=ts`) | NestJS (`--lang=nestjs`) | React (`--lang=react`) | AWS (`--lang=aws`) | Python (`--lang=python` or `--lang=py`) | |-------------|--------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|------------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------| | Debugger | `developer-kit:general-debugger` | `developer-kit:general-debugger` | `developer-kit:general-debugger` | `developer-kit:general-debugger` | `developer-kit:general-debugger` | `developer-kit:general-debugger` | `developer-kit:general-debugger` | | Architect | `developer-kit:general-software-architect` | `developer-kit-java:java-software-architect-review` | `developer-kit-typescript:typescript-software-architect-review` | `developer-kit-typescript:typescript-software-architect-review` | `developer-kit-typescript:react-software-architect-review` | `developer-kit-aws:aws-solution-architect-expert` | `developer-kit-python:python-software-architect-expert` | | Code Review | `developer-kit:general-code-reviewer` | `developer-kit-java:spring-boot-code-review-expert` | `developer-kit-typescript:general-code-reviewer` | `developer-kit-typescript:nestjs-code-review-expert` | `developer-kit-typescript:general-code-reviewer` | `developer-kit-aws:aws-architecture-review-expert` | `developer-kit-python:python-code-review-expert` |

Core Principles

• **Understand before fixing**: Never fix what you don't understand
• **Find root cause**: Symptoms can be deceiving - trace back to the real issue
• **Minimal changes**: Fix only what's broken, avoid scope creep
• **Verify completely**: Confirm the fix works and doesn't break other things
• **Use TodoWrite**: Track all progress throughout
• **Structured user interaction — NEVER SKIP**: Phases marked with **[GATE]** STOP are hard gates. You MUST call the

AskUserQuestion tool and wait for the user's response before proceeding. Skipping these stops or proceeding without user input is a workflow violation. Use AskUserQuestion in Phase 1: Problem Capture, Phase 3: Root Cause Analysis, Phase 4: Fix Design, and Phase 7: Verification. Always use AskUserQuestion for clarifications, confirmations, and decisions rather than plain text questions.

• **No time estimates**: DO NOT provide or request time estimates or implementation timelines at any phase

---

Phase 1: Problem Capture

**Goal**: Understand exactly what's wrong

**Initial issue**: $ARGUMENTS

**Actions**:

1. Create todo list with all phases 2. Gather problem details:

• What is the exact error message or unexpected behavior?
• When did this start happening?
• Can you reproduce it consistently?
• What are the reproduction steps?
• Any recent changes that might be related?

3. **You MUST call the AskUserQuestion tool to gather all missing information in a clear, organized format**:

• Error messages, logs, or stack traces
• Steps to reproduce
• Expected vs actual behavior
• Environment details (local, staging, production)

4. ****[GATE]** STOP: Wait for the user's answers. Do NOT proceed to Phase 2 until the user has responded.**

---

Phase 2: Evidence Collection

**Goal**: Gather all relevant information about the failure

**Actions**:

1. Use the Task tool to launch 2-3 general-debugger subagents in parallel with different focuses:

• Analyze stack traces an