ce-debug

A structured root cause tracing workflow systematically guides you through Triage, Investigate, Root Cause, Fix, and Handoff phases. It enforces one-change-at-a-time testing and evidence-driven diagnosis to identify true causal chains from trigger to symptom.

To debug a reproduced issue report, input the detailed bug description to initiate a phased debugging workflow. This process evaluates the issue tracker context, enforces predictive validation, and outputs actionable artifacts including root-cause descriptions and proposed fixes.

Yes, a phased debugging workflow applies to failing tests and code review troubleshooting. It enforces one-change-at-a-time testing and predictive validation to trace the full causal chain, ensuring fixes are evidence-driven and verifiable.

The best way to fix a bug is enforcing a one-change-at-a-time testing approach within a structured workflow. This ensures evidence-driven diagnosis, predictive validation, and generates validation guidance to verify the proposed fix.

You should not use a structured debugging workflow for trivial issues requiring immediate fixes. It enforces a five-phase process and one-change-at-a-time testing, which may introduce unnecessary overhead for simple errors lacking complex causal chains.

No, the ce-debug skill requires no dependencies or components to trace errors. You simply describe the bug in detail to start the structured five-phase workflow for identifying root causes and crafting verifiable fixes.