skills.rest
raybird
raybirdCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Systematize software debugging through a four-phase process of investigation, analysis, hypothesis testing, and implementation.

1|Updated Jan 28, 2026
Search Tags:#testing#debugging#root cause#troubleshooting#systematic#reliability
One-click install
npx skills add https://github.com/raybird/telenexus --skill systematic-debugging-raybird
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/raybird/telenexus/tree/main/skills/tao-of-opencode/references/superpowers/systematic-debugging
Command: npx skills add https://github.com/raybird/telenexus --skill systematic-debugging-raybird

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill prevents the common trap of wasting time on random fixes and symptom-masking patches by enforcing a disciplined, four-phase investigation process that ensures you identify and resolve the actual root cause of any technical issue.

Core Features & Use Cases

  • Four-Phase Framework: Guides you through investigation, pattern analysis, hypothesis testing, and implementation.
  • Anti-Shortcut Protection: Explicitly identifies and warns against common rationalizations like "I'm in a hurry" or "this is just a simple bug."
  • Multi-Layer Validation: Provides techniques like defense-in-depth and condition-based waiting to make bugs structurally impossible to reproduce.
  • Use Case: Use this when you are stuck on a flaky test or a production bug and find yourself tempted to apply "quick fixes" that don't seem to stick.

Quick Start

Load the systematic-debugging skill and follow the Phase 1 checklist to trace the root cause of the current test failure.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of a flaky test instead of just patching the symptom?▼

To find the root cause of a flaky test, you need a systematic debugging framework that enforces a strict four-phase process of investigation, pattern analysis, hypothesis testing, and implementation before modifying any code.

What is the best way to debug production bugs in a complex multi-component architecture?▼

The best way to debug production bugs across complex architectures is to apply a disciplined, root-cause-first framework that mandates thorough investigation and hypothesis testing to prevent architectural regression from quick fixes.

How do I stop applying quick fixes that fail to resolve recurring software defects?▼

To stop applying ineffective quick fixes, use an anti-shortcut debugging process that explicitly warns against rationalizations and requires multi-layer validation to make bugs structurally impossible to reproduce.

Can I use a systematic troubleshooting approach for unexpected system behaviors and not just crashes?▼

Yes, you can use systematic troubleshooting for unexpected system behaviors because the root-cause-first framework applies broadly to test failures, production bugs, and any unexpected multi-component system issues.

When should I avoid symptom-based patching during software troubleshooting?▼

You should avoid symptom-based patching whenever you are tempted to apply quick fixes to complex defects, as modifying code without strict root cause identification risks masking symptoms and causing deeper architectural regression.

Does systematic debugging require any specific testing frameworks or dependencies to start?▼

Systematic debugging requires no specific testing frameworks or dependencies, making it broadly applicable to any software defect investigation across diverse multi-component architectures and technology stacks.

Related Skills

Explore More Software Engineering Skills→
bjornjeebjornjee
19

fix

Reproduce a software defect in an isolated git worktree, then validate a minimal fix with tests.

Community
Advanced
benjgradbenjgrad

systematic-debugging

Diagnose software bugs through four non-skippable root-cause investigation phases.

Community
Advanced
MathiasPaulenkoMathiasPaulenko

jmeter-load-testing

Execute Apache JMeter load tests with JSR223 Groovy scripting.

Community
Advanced
kimen-devkimen-dev

systematic-debugging

Diagnose software defects through a four-phase root cause analysis methodology.

Official
Advanced