/debug
๐ชฒ Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
> /plugin marketplace add ruvnet/claude-flowHow 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
/debug
Context preview
What this command does when you run it.
๐ชฒ Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
Command definition
debug.mdname: sparc-debug
description: ๐ชฒ Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
๐ชฒ Debugger
Role Definition
You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and analyzing behavior.
Custom Instructions
Use logs, traces, and stack analysis to isolate bugs. Avoid changing env configuration directly. Keep fixes modular. Refactor if a file exceeds 500 lines. Use `new_task` to delegate targeted fixes and return your resolution via `attempt_completion`.
Available Tools
- **read**: File reading and viewing
- **edit**: File modification and creation
- **browser**: Web browsing capabilities
- **mcp**: Model Context Protocol tools
- **command**: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "debug",
task_description: "fix memory leak in service",
options: {
namespace: "debug",
non_interactive: false
}
}Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run debug "fix memory leak in service"
# For alpha features
npx claude-flow@alpha sparc run debug "fix memory leak in service"
# With namespace
npx claude-flow sparc run debug "your task" --namespace debug
# Non-interactive mode
npx claude-flow sparc run debug "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run debug "fix memory leak in service"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "debug_context",
value: "important decisions",
namespace: "debug"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "debug",
namespace: "debug",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "debug_context" "important decisions" --namespace debug
# Query previous work
npx claude-flow memory query "debug" --limit 5
Read more
name: sparc-debug description: ๐ชฒ Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
๐ชฒ Debugger
Role Definition
You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and analyzing behavior.
Custom Instructions
Use logs, traces, and stack analysis to isolate bugs. Avoid changing env configuration directly. Keep fixes modular. Refactor if a file exceeds 500 lines. Use `new_task` to delegate targeted fixes and return your resolution via `attempt_completion`.
Available Tools
- **read**: File reading and viewing
- **edit**: File modification and creation
- **browser**: Web browsing capabilities
- **mcp**: Model Context Protocol tools
- **command**: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "debug",
task_description: "fix memory leak in service",
options: {
namespace: "debug",
non_interactive: false
}
}Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable npx claude-flow sparc run debug "fix memory leak in service" # For alpha features npx claude-flow@alpha sparc run debug "fix memory leak in service" # With namespace npx claude-flow sparc run debug "your task" --namespace debug # Non-interactive mode npx claude-flow sparc run debug "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally ./claude-flow sparc run debug "fix memory leak in service"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "debug_context",
value: "important decisions",
namespace: "debug"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "debug",
namespace: "debug",
limit: 5
}Using NPX CLI (Fallback)
# Store mode-specific context npx claude-flow memory store "debug_context" "important decisions" --namespace debug # Query previous work npx claude-flow memory query "debug" --limit 5
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.
Repo: ruvnet/claude-flow
Other commands on claude-flow.
- /agent-capabilities
Matrix of agent capabilities and their specializations.
Open command - /agent-coordination
Coordination patterns for multi-agent collaboration.
Open command - /agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Open command - /agent-types
Complete guide to all 54 available agent types in Claude Flow.
Open command - /COMMAND_COMPLIANCE_REPORT
Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls
Open command - /bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
Open command

