Guide structured root-cause debugging with evidence gathering and hypothesis testing.
npx skills add https://github.com/alexiolan/craft-skills --skill debug-alexiolan
Please help me install this Agent Skill. Skill: debug Source: https://github.com/alexiolan/craft-skills/tree/main/skills/debug Command: npx skills add https://github.com/alexiolan/craft-skills --skill debug-alexiolan
Helps engineers perform structured root-cause debugging before writing any patch, reducing wasted effort and regression risk.
Describe the bug, reproduce it reliably, and follow the root-cause investigation workflow before proposing any fix.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging enforces a structured investigation workflow with error reproduction, evidence gathering, and hypothesis testing before implementing any code fix. This prevents premature patches and reduces regression risk.
A structured debugging session follows Phase 1–4 investigation phases, guiding systematic data collection, hypothesis formation, and controlled implementation. This ensures fixes are based on verified evidence rather than guesswork.
To stop premature fixes, follow an anti-pattern control workflow that enforces formal evidence collection and escalation rules before proposing any code changes. This guarantees reliable error reproduction is achieved first.
You need structured root-cause investigation when facing complex software bugs where wasted effort and regression risk are high. It enforces evidence gathering and hypothesis testing to ensure safe implementation of fixes.
Yes, hypothesis-driven debugging formalizes evidence collection and hypothesis testing during quality assurance workflows. It enforces investigation phases and anti-pattern controls to guide safe, controlled implementation of fixes.
Skipping evidence gathering leads to wasted effort and higher regression risk because fixes are applied without reliable error reproduction or root-cause verification. Structured investigation phases and escalation rules are required to prevent this.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
balic-AI-ML-R-D-ResourcesReview security patches for root-cause coverage and bypass risks.
bigeasyfreemanDebug code errors through evidence collection, hypothesis testing, and verification.
nicolas-deyrosEnforce a four-phase workflow for root-cause debugging of bugs and test failures.
