Enforce a four-phase debugging methodology for root cause analysis.
npx skills add https://github.com/edlng/agents --skill systematic-debugging-edlng
Please help me install this Agent Skill. Skill: systematic-debugging Source: https://github.com/edlng/agents/tree/main/skills/universal/systematic-debugging Command: npx skills add https://github.com/edlng/agents --skill systematic-debugging-edlng
This skill eliminates the cycle of random, ineffective patches and time-wasting "guess-and-check" debugging by enforcing a rigorous, evidence-based investigation process.
Activate the systematic debugging skill to begin a structured investigation of the current test failure or production bug.
High-intent search queries and answers about installing and using this skill.
To find the root cause of intermittent production failures, apply an evidence-based investigation process that traces data flow across component boundaries rather than blindly adding retry logic or timeouts.
The best way to stop guess-and-check debugging is to enforce a rigorous four-phase methodology: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring you validate before changing code.
To systematically debug test failures, activate a structured investigation framework that requires evidence-based hypothesis testing and architectural validation before implementing any code patches.
Yes, you can use this systematic debugging process for complex system performance problems, as it enforces tracing data flow and validating hypotheses across component boundaries before applying fixes.
You should not use structured root cause analysis when bypassing investigation for a quick patch, as anti-shortcut guardrails explicitly block rationalizations like "this is just a simple fix" to ensure reliability.
Yes, systematic debugging works by eliminating random, ineffective patches through pattern analysis and hypothesis testing, forcing you to validate architectural boundaries instead of applying superficial fixes.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
KrismithReddy12Perform adversarial code review and diff analysis for software engineering projects.
yonatangrossValidate API boundaries and cross-service contracts with Pact, Supertest, httpx, and Hypothesis.
valtterimelkkoInvestigate root causes through a four-phase debugging framework before modifying code.
