Skip to content
Development
Command

/debugger

Systematic debugging with TodoWrite and Memory integration.

From plugin
claude-flow
67k194 skills157 agents194 commands1 MCP
Install
> /plugin marketplace add ruvnet/claude-flow

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/debugger

Context preview

What this command does when you run it.

Systematic debugging with TodoWrite and Memory integration.

Command definition

debugger.md

SPARC Debugger Mode

Purpose

Systematic debugging with TodoWrite and Memory integration.

Activation

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "debugger",
  task_description: "fix authentication issues",
  options: {
    verbose: true,
    trace: true
  }
}

Option 2: Using NPX CLI (Fallback when MCP not available)

# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run debugger "fix authentication issues"

# For alpha features
npx claude-flow@alpha sparc run debugger "fix authentication issues"

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run debugger "fix authentication issues"

Core Capabilities

  • Issue reproduction
  • Root cause analysis
  • Stack trace analysis
  • Memory leak detection
  • Performance bottleneck identification

Debugging Workflow

1. Create debugging plan with TodoWrite 2. Systematic issue investigation 3. Store findings in Memory 4. Track fix progress 5. Verify resolution

Tools Integration

  • Error log analysis
  • Breakpoint simulation
  • Variable inspection
  • Call stack tracing
  • Memory profiling
Ships withclaude-flow

An agent meta-harness for Claude Code and Codex. Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work.

Get the whole plugin