gstack-investigate

Root cause analysis for software bugs requires a structured, four-phase workflow: investigate, analyze, hypothesize, and implement. This enforces evidence-based debugging by requiring explicit root cause confirmation before applying any code fixes.

Debugging a 500 error using a stack trace involves gathering repository context, analyzing the trace, and forming hypotheses. A strict investigation workflow ensures you identify the exact failure point and confirm the root cause before writing a fix.

Troubleshooting a software regression involves routing the broken behavior through a systematic investigation process. By querying repository context and prior learnings, you can form accurate hypotheses about what changed and confirm the root cause before implementing a fix.

Applying code fixes immediately during error triage is blocked by this workflow. It enforces a strict rule of no fixes without root cause confirmation, ensuring you only apply patches justified by evidence from the stack trace or repository context.

Systematic root cause investigation uses tool-gated execution with bash, grep, read, write, edit, and glob to query repository context. This structured approach gathers evidence and tests hypotheses before you implement the actual code fix.