aio-debuglisted

# DebugFix - Systematic Debug & Fix Orchestrator ## Environment - git: !`git --version 2>/dev/null || echo "NOT INSTALLED"` Orchestrate four specialized skills in sequence to maximize debugging effectiveness. Each phase builds on the previous, ensuring root cause is found before any code changes, and all changes are reviewed before completion. ## Orchestration Flow — Skill Graph ``` Phase 1: Understand Context /discover (AIO) + /deep-dive (OMC) | Phase 2: Investigate Root Cause /superpowers:systematic-debugging + /oh-my-claudecode:trace | Phase 3: Implement Fix /superpowers:test-driven-development (TDD) | Phase 4: Verify & Review /superpowers:verification-before-completion → /aio-review-deep ``` ## Phase 1: Understand Context Before debugging, understand the surrounding codebase using discovery skills: 1. Invoke `/discover` with the bug description — finds relevant files via GitNexus 2. For complex bugs spanning multiple modules, also invoke `/oh-my-claudecode:deep-dive` for deeper analysis 3. Identify: affected files, data flow, dependencies, recent changes to the area 4. Map the execution path from input to where the bug manifests **Exit criteria**: Clear understanding of the code area, its patterns, and its dependencies. ## Phase 2: Investigate Root Cause With codebase context established, apply systematic debugging rigor: 1. Invoke `/superpowers:systematic-debugging` — the gold standard 4-phase debugging methodology 2.