Coordinate root-cause debugging workflows into a repeatable four-phase process.
npx skills add https://github.com/mi179/claude-skills --skill investigate-mi179
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/gstack/investigate Command: npx skills add https://github.com/mi179/claude-skills --skill investigate-mi179
Root-cause debugging workflows are often ad hoc and time-consuming. This skill provides a repeatable four-phase process (investigate, analyze, hypothesize, implement) to systematically identify root causes before applying fixes.
Describe the failure, gather logs and signals, then begin the investigate–analyze–hypothesize–implement cycle.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging uses a structured four-phase process—investigate, analyze, hypothesize, implement—to collect evidence and validate fixes before applying changes. This prevents premature fixes by enforcing a repeatable workflow across projects and services.
Debugging a stack trace across services requires a coordinated investigation workflow that gathers logs and signals first. A guided approach enforces evidence collection and hypothesis validation before any implementation changes are made to the codebase.
Troubleshooting an incident without premature fixes requires a four-phase cycle: investigate signals, analyze data, hypothesize root causes, and implement validated changes. This structured approach uses guardrails to ensure fixes are backed by collected evidence.
Yes, you can use Bash, Grep, Read, Write, Edit, Glob, WebSearch, and AskUserQuestion to collect evidence and brainstorm hypotheses. These tools support the investigation and analysis phases by gathering logs, searching codebases, and validating proposed root causes.
Ad hoc debugging is time-consuming and often leads to premature fixes without identifying the true root cause. A structured four-phase workflow overcomes this by enforcing evidence collection and hypothesis validation before implementing changes across projects.
Guided root-cause debugging applies to error investigations, stack traces, and incidents across multiple projects and services. It coordinates the debugging workflow into a repeatable process regardless of the specific codebase or service architecture.
jk278Diagnose software bugs from stack traces and error logs.
KodingDevIdentify and resolve root causes of bugs and test failures.
TobiasPerryDiagnoses root causes of bugs by analyzing logs, code, and evidence.
mwayIdentify root causes of bugs and test failures through a four-phase debugging workflow.
