Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Detected risks:
The systematic-debugging skill is designed to assist developers and engineers in effectively identifying and resolving bugs, test failures, and unexpected behaviors in their code. It addresses the common problem of implementing random fixes that may temporarily alleviate symptoms but ultimately lead to more significant issues down the line. By emphasizing the importance of root cause investigation before any fixes are proposed, this skill helps to streamline the debugging process and reduce time wasted on ineffective solutions.
Use this skill for any technical issue, including test failures, bugs in production, unexpected behavior, performance problems, build failures, and integration issues.
The process consists of four phases: Root Cause Investigation, Pattern Analysis, Fix Implementation, and Validation.
No, you should not skip any phases, as even simple issues may have underlying root causes that need to be addressed.
There are no specific environment requirements mentioned, but ensure you have access to the relevant codebase and tools for debugging.
Yes, the skill includes specific guidance for gathering evidence in multi-component systems before proposing fixes.
Quick Setup:
.claude/skills/Repository
obra/superpowers