systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Install with Tessl CLI
npx tessl i github:projectbluefin/dakota --skill systematic-debugging63
Quality
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/systematic-debugging/SKILL.mdEvaluation results
Failed
Root cause investigation before fixes with four-phase sequential process
Failed
Diagnostic instrumentation at component boundaries and backward root cause tracing
Failed
Defense-in-depth validation at multiple layers after root cause fix
Failed
Three-fix architectural escalation and recognizing when to stop fixing symptoms
Failed
Condition-based waiting replacing arbitrary timeouts in flaky tests
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Root cause investigation before fixes with four-phase sequential processDiagnostic instrumentation at component boundaries and backward root cause tracingDefense-in-depth validation at multiple layers after root cause fixThree-fix architectural escalation and recognizing when to stop fixing symptomsCondition-based waiting replacing arbitrary timeouts in flaky tests
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.