skills.rest
danlawless
danlawlessCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured root cause analysis of technical issues through hypothesis testing.

Updated Aug 10, 2025
Search Tags:#testing#debugging#problem solving#troubleshooting#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/danlawless/busybees --skill systematic-debugging-danlawless
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/danlawless/busybees/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/danlawless/busybees --skill systematic-debugging-danlawless

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the frustration and inefficiency of debugging by providing a structured, evidence-based approach to identify and resolve the root cause of technical issues, preventing superficial fixes and recurring problems.

Core Features & Use Cases

  • Root Cause Analysis: Guides users through a systematic process to understand why a problem occurs before attempting a fix.
  • Evidence-Based Debugging: Emphasizes starting with error messages, stack traces, and reproduction steps.
  • Hypothesis Testing: Encourages forming and testing clear hypotheses with minimal changes.
  • Use Case: When a critical feature suddenly starts failing in production after a recent deployment, this Skill helps engineers methodically trace the data flow backward from the error to pinpoint the exact faulty logic or configuration, ensuring a correct and lasting solution.

Quick Start

Use the systematic-debugging skill to analyze the recent test failures in the CI pipeline.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a bug in production?▼

Root cause analysis for production bugs requires tracing data flow backward from the error. This approach uses evidence like error messages and stack traces to pinpoint faulty logic, ensuring a correct and lasting solution.

How do I debug failing tests in a CI pipeline systematically?▼

Debugging failing tests systematically involves starting with reproduction steps and error messages. You form testable hypotheses, implement minimal targeted fixes, and trace data flow to identify the root cause of the test failures.

Why does my bug fix keep causing the same unexpected behavior?▼

Unexpected behavior recurs when fixes address symptoms rather than the root cause. An evidence-based debugging process emphasizes understanding why a problem occurs by tracing data flow and verifying hypotheses before implementing changes.

How do I troubleshoot an issue when multiple bug fixing attempts fail?▼

When multiple bug fixing attempts fail, you should recognize and address underlying architectural problems. This structured process guides you to evaluate architectural issues after repeated targeted fixes do not resolve the technical issue.

Does evidence-based debugging work without stack traces or error messages?▼

Evidence-based debugging relies on error messages, stack traces, and reproduction steps as starting points. Without these inputs, forming testable hypotheses and tracing data flow backward to the root cause becomes significantly more difficult.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
VYRE-StudiosVYRE-Studios

systematic-debugging

Debug software by reproducing, isolating, hypothesizing, verifying, and fixing issues.

Official
Advanced
AllBeingsFutureAllBeingsFuture
9

obra/superpowers@systematic-debugging

Identify root causes of software bugs through a four-phase debugging workflow.

Community
Advanced
iani-kuliiani-kuli

investigate

Perform systematic root cause analysis for software errors and regressions.

Community
Advanced