Identify root causes of software bugs through a structured four-phase debugging workflow.
npx skills add https://github.com/westn/gstack-pi-port --skill investigate-westn
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/investigate Command: npx skills add https://github.com/westn/gstack-pi-port --skill investigate-westn
Systematic debugging primed to uncover the root cause of software issues rather than treating symptoms.
Describe the issue clearly and run /skill:investigate to begin the root-cause analysis.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging uses an evidence-first, phase-driven workflow to investigate, analyze, hypothesize, and implement fixes. It requires clear symptom data, code access, and permission to add logging to validate hypotheses before patching.
Debugging a stack trace systematically involves collecting symptoms, reading code paths, reproducing steps, and logging findings. This structured approach avoids guesswork by validating hypotheses against evidence to uncover the real problem.
Triaging failing tests uses a four-phase workflow: investigate, analyze, hypothesize, and implement. You read code paths and add targeted logging to reproduce steps and confirm the root cause before applying a fix.
Yes, structured log analysis is an evidence-first approach to reproduce steps for a crash. By reading code paths and logging findings, you validate hypotheses to identify the deterministic root cause before patching.
Yes, investigating a code error requires permission to add logging or tests to confirm hypotheses. You also need clear symptom data and access to the relevant code paths to successfully identify the root cause.
You should switch to systematic code reading for triage when a user reports an error and the root cause is not obvious. A structured investigation prevents treating symptoms by validating hypotheses against collected evidence first.
jk278Diagnose software bugs from stack traces and error logs.
abranjithDiagnose software bugs, apply minimal fixes, and add regression tests.
jasonwilmotCoordinate a structured debugging workflow to reproduce and resolve software bugs.
LazyNinja435Investigate, test hypotheses, and implement root cause fixes for technical issues.
