Diagnose software failures through a four-phase root-cause investigation workflow.
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill investigate-bradliebs
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.gstack/investigate Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill investigate-bradliebs
Systematic debugging with root-cause investigation to identify underlying issues rather than patching symptoms.
Describe the bug to start the root-cause investigation and let the skill guide the four phases to surface the real fix.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging identifies the underlying source of software failures using evidence like stack traces and logs, ensuring durable resolutions rather than temporarily patching symptoms.
Debug a stack trace through a four-phase workflow: investigate, analyze, hypothesize, and implement. Gather contextual data using Grep, Read, and WebSearch to surface the verified root cause.
Investigate unexpected behavior by gathering evidence from code, configurations, and deployments, enforcing an Iron Law that requires verified root cause evidence before applying any fixes.
Yes, systematic debugging applies to errors and unexpected behavior across code, configurations, and deployments, guiding you through investigation phases to implement fixes based on verified evidence.
Avoid patching symptoms because the Iron Law of root-cause analysis mandates that no fixes be applied without verified root cause evidence, ensuring the underlying issue is durably resolved.
rahmanayonPlan root-cause investigations across investigate, analyze, hypothesize, and implement phases.
willdadyDiagnose software bugs through a structured six-phase feedback loop.
mi179Coordinate root-cause debugging workflows into a repeatable four-phase process.
ClaudioCeppi83Analyze error patterns and stack traces to identify root causes.
