Debug software issues through four root-cause investigation phases.
npx skills add https://github.com/ingoatl/propertycentral --skill investigate-ingoatl
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/investigate Command: npx skills add https://github.com/ingoatl/propertycentral --skill investigate-ingoatl
Root-cause debugging for software issues is hard and error-prone. This skill provides a disciplined, four-phase framework to systematically uncover the true cause before attempting fixes.
Begin by collecting symptoms, tracing code paths, and following the four phases to identify the root cause before implementing a fix.
High-intent search queries and answers about installing and using this skill.
The four phases of root-cause debugging are investigate, analyze, hypothesize, and implement. This structured workflow enforces collecting symptoms, tracing code paths, testing hypotheses, and verifying fixes before deployment.
The best way to investigate crashes and performance anomalies is a structured root-cause analysis workflow. It guides you to collect symptoms, check recent changes, read code paths, and reproduce the issue before attempting fixes.
Hypothesis-testing in debugging works by locking scope after the investigation and analysis phases. You form a hypothesis about the root cause, then use tools like Bash and Grep to verify data and reason about the code before implementing a fix.
Yes, this root-cause analysis workflow explicitly covers user-reported bugs. It systematically guides you through collecting symptoms, tracing code paths, and reproducing the issue across code, tests, and deployments.
You should escalate during root-cause analysis when facing uncertain cases after the investigate and analyze phases. The workflow provides clear escalation guidelines for uncertain cases and ensures safe handling of complex debugging scenarios.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
divad12Write a failing regression test before tracing the root cause and fixing the bug.
LaPaGaYoGuide users through a four-phase debugging workflow to diagnose root causes.
abranjithDiagnose software bugs, apply minimal fixes, and add regression tests.
