Guide root-cause debugging through a four-phase investigation and verification process.
npx skills add https://github.com/dige04/hieu-ccsetup --skill debugging-dige04
Please help me install this Agent Skill. Skill: Debugging Source: https://github.com/dige04/hieu-ccsetup/tree/main/config/skills/debugging Command: npx skills add https://github.com/dige04/hieu-ccsetup --skill debugging-dige04
Comprehensive debugging framework combining systematic investigation, root cause tracing, defense-in-depth validation, and verification protocols.
Follow the four-phase debugging process to identify the root cause before applying fixes.
High-intent search queries and answers about installing and using this skill.
Systematic root cause debugging is a structured investigation process to uncover why software failures occur. You should use it when confronting bugs, test failures, performance issues, or integration problems to ensure no fixes are applied without root cause data.
Trace root causes by performing backward call stack analysis with targeted instrumentation. This method traces execution backward from the failure point, using instrumentation guidance to collect the data needed to identify the exact origin of the bug.
The best way to verify a fix is by running fresh checks and collecting evidence. Defense-in-depth validation across entry, business logic, environment guards, and debug instrumentation layers ensures the fix is thoroughly verified before completion.
Find the root cause of test failures by following a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation. This enforces systematic investigation to prevent applying fixes without underlying data.
Yes, this debugging framework applies across software debugging scenarios including performance issues and integration problems. It enforces a systematic four-phase process to uncover root causes and applies defense-in-depth validation regardless of the bug type.
Fixing bugs without pattern analysis and hypothesis testing risks addressing symptoms rather than root causes. Skipping these phases means lacking verification evidence and defense-in-depth validation, which can lead to recurring failures and unresolved integration issues.
Ilenburg1993Analyze stack traces and logs to identify root causes and apply minimal patches.
levanminhducEnforce defense-in-depth validation across API boundaries, business logic, environment guards, and debug instrumentation.
Mentor-WizardAnalyze stack traces and identify root causes of code errors.
alexanderopDiagnose software bugs through a four-phase root-cause investigation process.
