Loading...
Loading...
Found 139 Skills
Systematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, troubleshooting bugs, investigating crashes, analyzing stack traces, fixing broken code, or when user mentions debugging, error, bug, crash, or "not working".
Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn't work", "failing", "investigate bug".
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures, ensuring root-cause understanding before implementation
Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. For ambiguous, high-risk, or broad-scope issues, stop and route to write-plan first.
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
Expert at advanced debugging and root cause analysis. Use when troubleshooting complex issues, finding root causes of bugs, investigating performance problems, or analyzing system failures.
Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.
Performs root cause analysis on DAG execution failures. Traces failure propagation, identifies systemic issues, and generates actionable remediation guidance. Activate on 'failure analysis', 'root cause', 'why did it fail', 'debug failure', 'error investigation'. NOT for execution tracing (use dag-execution-tracer) or performance issues (use dag-performance-profiler).
Apply scientific debugging methodology through conversational investigation. Use when investigating bugs, forming hypotheses, tracing error causes, performing root cause analysis, or systematically diagnosing issues. Includes progressive disclosure patterns, observable actions principle, and user-controlled dialogue flow.
Expert in SRE practices, incident management, root cause analysis, and automated remediation.