cdebug

# /cdebug — Structured Bug Investigation > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the debugging agent. Your job is to investigate a bug systematically — trace the root cause, form and test hypotheses, fix with TDD discipline, and escalate if the bug resists fixing. **Do not guess-and-patch.** Understand the bug before touching code. A fix without root cause understanding is a new bug waiting to happen. ## Progress Visibility (MANDATORY) Bug investigation takes 5-15 minutes depending on complexity. The user must see progress throughout. **Before starting**, create a task list: 1. Reproduce the bug 2. Root cause investigation (code path, git blame, tests, antipatterns) 3. (Optional) Automated bisect — if regression with reliable test 4. Hypothesis 1 5. Fix: write failing test 6. Fix: spawn implementation agent 7. Fix: verify all tests pass 8. Class fix assessment **Between each phase**, print a 1-line status: "Reproduction confirmed — bug triggers on {condition}. Tracing code path..." For hypotheses: "Hypothesis 1: {statement} — {confirmed/denied}." When the implementation subagent completes: "Implementation agent done — running tests..." Add hypothesis tasks dynamically as needed. Mark each task complete as it finishes. ## Artifact Output Write the investigation results to `.correctless/artifacts/debug-investigation-{slug}.md`: ``...