Enforce root cause investigation before proposing fixes to bugs.
npx skills add https://github.com/LuizEduPP/skills --skill systematic-debugging-luizedupp
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/LuizEduPP/skills/tree/main/systematic-debugging Command: npx skills add https://github.com/LuizEduPP/skills --skill systematic-debugging-luizedupp
Root cause investigation is skipped when bugs appear, costing time and creating regressions and lingering symptoms in tests, builds, and production flows. This Skill forces pause, evidence gathering, and mandated research before any code change.
Ask for systematic-debugging before touching the code whenever you observe a failing test, error message, or unexpected behavior and need a reliable fix.
High-intent search queries and answers about installing and using this skill.
Root cause investigation requires documenting evidence, comparing working references, and testing single hypotheses before changing code. This structured debugging approach enforces evidence gathering and failing tests to guarantee regressions are avoided.
Debugging production outages safely demands pressure-resistant guardrails and single-hypothesis testing before any fix. This method mandates evidence collection and condition-based waiting to prevent irrational shortcuts during urgent incidents.
To stop hasty patches, enforce a four-phase workflow: document evidence, compare patterns, formulate single hypotheses, and implement tests-only fixes. This prevents bug investigation shortcuts that introduce lingering symptoms in builds.
Systematic debugging targets integration failures and test-driven development pipelines by enforcing root cause tracing. It mandates failing tests documented before changes, ensuring fixes address unexpected behavior across testing environments.
Avoid trial-and-error patching whenever a failing test, error message, or unexpected behavior appears. Skipping root cause investigation costs time and creates regressions, demanding disciplined evidence gathering and architectural stop points instead.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
chriswesttIdentify bug root causes through symptom collection, code path tracing, and deterministic reproduction.
obraGuide software debugging through a four-phase root cause investigation process.
bhianerdGuide root-cause debugging with evidence collection and hypothesis validation.
