Stats
Actions
Tags
From exarchos
Starts a structured debug workflow for bugs and regressions, with hotfix, thorough, and escalate tracks. Guides triage, root-cause analysis, validation, and merge confirmation.
How this command is triggered — by the user, by Claude, or both
Slash command
/exarchos:debugFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Debug Start debug workflow for: "$ARGUMENTS" ## Workflow Overview Debug workflows are **investigation-first**: understand the problem before fixing it. **Single human checkpoint:** Merge confirmation (after fix is validated). ## Skill Reference Follow the debug skill: `@skills/debug/SKILL.md` ## Command Variants ### Default: Thorough Track Full investigation with RCA documentation. ### Fast Path: Hotfix Track Time-boxed investigation (15 min), minimal ceremony. ### Escalate: Feature Workflow Handoff Hands off to `/exarchos:ideate` with preserved context. ### Mid-Work...
Start debug workflow for: "$ARGUMENTS"
Debug workflows are investigation-first: understand the problem before fixing it.
/exarchos:debug → Triage → Investigate → [Fix] → Validate → [CONFIRM] → merge
│
┌─────────────┼─────────────┐
│ │ │
--hotfix (default) --escalate
│ │ │
Fast path Thorough path → /exarchos:ideate
(15 min) (full RCA)
Single human checkpoint: Merge confirmation (after fix is validated).
Follow the debug skill: @skills/debug/SKILL.md
/exarchos:debug "Users report cart total is wrong after removing items"
Full investigation with RCA documentation.
/exarchos:debug --hotfix "Production login is returning 500 errors"
Time-boxed investigation (15 min), minimal ceremony.
/exarchos:debug --escalate "This requires redesigning the auth system"
Hands off to /exarchos:ideate with preserved context.
/exarchos:debug --switch-thorough
Switch from hotfix to thorough track during investigation.
Initialize workflow state using mcp__plugin_exarchos_exarchos__exarchos_workflow with action: "init":
featureId to debug-<issue-slug>workflowType to "debug"Then update the track using mcp__plugin_exarchos_exarchos__exarchos_workflow with action: "update":
track to "hotfix" or "thorough" based on triageGather context using @skills/debug/references/triage-questions.md:
Select track based on urgency and complexity.
On the thorough track, the rca and design phases are the design-time surfaces. Before committing to a fix approach, load the invariants catalog at .exarchos/invariants.md (entries marked cost-of-load: always-load) and surface a Constraints section naming the invariants relevant to the fix. This is the debug design-time equivalent of /ideate's Phase 0 and uses the same single shared source of truth for the selection rules and devCatalog gating: @skills/brainstorming/references/constraint-anchoring.md. devCatalog-gated: when .exarchos.yml: invariants.devCatalog: enabled is unset or disabled, surface no Constraints section and proceed directly. The hotfix track skips this step (speed over ceremony).
Hotfix Track:
Thorough Track:
| Argument | Effect |
|---|---|
<description> | Bug description for triage context |
--hotfix | Select hotfix track (P0 urgency) |
--escalate | Hand off to /exarchos:ideate workflow |
--switch-thorough | Switch from hotfix to thorough mid-workflow |
Debug workflows use extended state schema. See @skills/debug/references/state-schema.md.
Key fields:
workflowType: "debug"track: "hotfix" | "thorough"urgency: { level, justification }triage: { symptom, reproduction, affectedArea, impact }investigation: { rootCause, findings }Debug workflows auto-chain through phases with ONE human checkpoint.
Both tracks:
[all phases auto-chain] → merge confirmation (HUMAN)
Debug workflows resume via MCP auto-discovery:
/exarchos:rehydrate
| Signal | Use /exarchos:debug | Use /exarchos:refactor |
|---|---|---|
| Something is broken or wrong | Yes | No |
| Code works but is messy/complex | No | Yes |
| Users report a bug or regression | Yes | No |
| Performance degradation | Start with /exarchos:debug (investigate) | Escalate to /exarchos:refactor if structural |
| "This should be reorganized" | No | Yes |
| Error in production logs | Yes | No |
Rule of thumb: If there is a symptom (something that should work but doesn't), use /exarchos:debug. If there is dissatisfaction with working code (hard to read, violates SOLID, duplicated logic), use /exarchos:refactor.
@skills/debug/references/rca-template.md@skills/debug/references/triage-questions.md@skills/debug/references/investigation-checklist.md@skills/debug/references/state-schema.mdnpx claudepluginhub lvlup-sw/exarchos/debugExecutes systematic debugging workflow end-to-end: triage issue from description, diagnose root cause, plan fix, and execute using persistent state and tools like Read, Bash, Edit.
/troubleshootExecutes 5-step debugging loop (research, hypothesize, implement, test, document) for unexpected issues during tasks or standalone bugs, updating WORKLOG.md.
/fire-debugDebugs issues using scientific method with subagent isolation, persistent state recovery, and skills library integration. Supports --diagnose-only and --verbose flags.
/debugRuns structured debugging with parallel agents: traces bugs via phases, diagnoses root causes with evidence, proposes minimal fixes, executes after approval. Tracks in tasks/todo.md.
/hatch3r-debugInstruments code with debug logging, collects runtime logs from the user, performs root cause analysis, implements the fix, and removes all debug artifacts.
/debugRuns a 4-phase systematic debugging investigation (root cause, pattern, impact, solution) and writes an artifact to .orchestrator/debug/ before any fix is proposed.