skills.rest
SufficientDaikon
SufficientDaikonCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide root cause analysis through four structured debugging phases before fixes.

8|Updated Mar 8, 2026
Search Tags:#testing#debugging#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/SufficientDaikon/omniskill --skill systematic-debugging-sufficientdaikon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/SufficientDaikon/omniskill/tree/main/.cursor/rules/systematic-debugging
Command: npx skills add https://github.com/SufficientDaikon/omniskill --skill systematic-debugging-sufficientdaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by enforcing a rigorous, four-phase process to ensure root cause investigation before any fixes are attempted. It combats the common tendency to apply quick, superficial patches.

Core Features & Use Cases

  • Four-Phase Debugging: Guides users through Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
  • Strict Enforcement: Mandates completion of each phase before proceeding, preventing premature fixes.
  • Use Case: When a critical test fails in a CI/CD pipeline, this Skill ensures the AI meticulously investigates the error messages, reproduces the failure, checks recent changes, and traces data flow to pinpoint the exact source of the problem before suggesting any code modifications.

Quick Start

Use the systematic-debugging skill to investigate any bug or test failure you encounter.

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 bug before attempting a fix?▼

To find the root cause of a bug before fixing, use a structured four-phase methodology that enforces error analysis, reproduction, and evidence gathering. This prevents superficial patches by mandating pattern analysis and hypothesis testing prior to implementation.

What is the best way to debug a failing test in a CI/CD pipeline?▼

The best way to debug a failing test in a CI/CD pipeline is to follow a phased approach: analyze error messages, reproduce the failure, review recent change history, and trace data flow to pinpoint the exact source before suggesting code modifications.

How do I trace data flow in multi-component systems to identify bug patterns?▼

Tracing data flow in multi-component systems requires gathering evidence across components and identifying patterns. A systematic debugging process guides you through data flow tracing and pattern identification to formulate precise, minimal testable hypotheses.

Why do my software bug fixes keep introducing new unexpected behavior?▼

Software bug fixes introduce new unexpected behavior when attempted before root cause investigation. Applying quick, superficial patches without reproducing the failure or testing hypotheses leads to incomplete resolutions and secondary issues.

When should I question software architecture during troubleshooting?▼

You should question software architecture during troubleshooting when multiple attempted fixes fail to resolve the unexpected behavior. Systematic debugging emphasizes architectural questioning as a final step after minimal testing and verified single fixes prove insufficient.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
kyo0221kyo0221

diagnose

Guide a 6-phase workflow to reproduce, diagnose, and fix software bugs.

Community
Advanced
roderikroderik
2

systematic-debugging

Investigate root causes through a four-phase debugging process.

Community
Advanced
uladzemeruladzemer
1

fable-thinking

Enforce proof-based verification and root-cause analysis for agentic coding tasks.

Community
Advanced