gstack-openclaw-investigate

Root-cause debugging involves collecting symptoms, tracing code paths, and generating testable hypotheses. This Skill structures that workflow into phases to identify underlying causes rather than chasing symptoms, concluding with a formal debug report.

The best way to structure a debugging investigation is using a phase-based workflow. This approach sequentially guides you through symptom collection, code-path tracing, reproduction steps, and hypothesis verification to ensure systematic defect diagnosis.

Yes, you can use this investigation workflow for production environment failures. It applies to debugging sessions, error reports, and failures encountered in both development and production environments to help diagnose software defects.

To generate a testable hypothesis from a stack trace, gather the error messages and reproduction steps, then run the investigation phases to trace the code paths. This forms an explicit root-cause hypothesis for verification.

Your debugging process may keep chasing symptoms because it lacks hypothesis-driven analysis. By applying structured root-cause investigation with explicit outputs and verification steps, you can identify underlying causes and prevent future regressions.