You MUST use this when ANY bug, test failure, exception, regression, or unexpected behavior appears — before proposing or applying any fix. Forces root-cause investigation. Do not use for the expected red phase of TDD — a new failing test you just wrote is progress, not a bug.
How to install systematic-debugging?
felipemelendez/llm-orchestrator/systematic-debugging
$npx -y skills add felipemelendez/llm-orchestrator --skill systematic-debuggingInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/felipemelendez/llm-orchestrator" --skill "felipemelendez/llm-orchestrator/systematic-debugging"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/felipemelendez/llm-orchestrator" that are relevant to the current task. Run `npx skills add "https://github.com/felipemelendez/llm-orchestrator"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.Jul 2026
- appinsights-instrumentationGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references.Jul 2026
- diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Jul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work.Jul 2026
- golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single…Jul 2026
