Guide engineers through a five-phase root-cause debugging workflow.
npx skills add https://github.com/putrawitama/DenchClaw --skill investigate-putrawitama
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/gstack/investigate Command: npx skills add https://github.com/putrawitama/DenchClaw --skill investigate-putrawitama
Helps engineers systematically debug by focusing on root-cause investigation before implementing fixes.
Begin by collecting symptoms and reproduction steps, then form a concrete root-cause hypothesis.
High-intent search queries and answers about installing and using this skill.
Structured root-cause debugging is a systematic workflow that identifies and fixes underlying software issues through evidence-based validation. It prevents repetitive fixes by guiding engineers through phases: investigate, analyze, hypothesize, implement, and verify.
To find the root cause of unexpected behavior, begin by collecting symptoms and reproduction steps, then form a concrete root-cause hypothesis. Analyze the evidence to validate the hypothesis before implementing and verifying the fix.
The best way to troubleshoot codebase errors is using a phase-based approach that emphasizes evidence-based validation. This ensures you verify the underlying issue systematically rather than applying repetitive surface-level fixes.
Yes, you can use hypothesis testing for general code analysis to systematically debug unexpected behavior. It structures your troubleshooting by requiring evidence-based validation of a root-cause hypothesis before you implement any code fixes.
You should not use a systematic debugging workflow for trivial syntax errors or obvious typos where the root cause is immediately visible. It is designed for complex troubleshooting requiring reproduction steps and rigorous verification across software systems.
scanbottDiagnose software bug root causes through a structured investigation workflow.
MissTullyDiagnose software issues through a phase-driven root-cause analysis workflow.
steadyfallGuide systematic root-cause debugging through investigate, analyze, hypothesize, and implement phases.
ag47-ptGuide structured debugging through reproduction, isolation, root cause analysis, and fix verification.
