skills.rest
LillianLi110130
LillianLi110130COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide root cause analysis of software bugs through investigation, hypothesis testing, and implementation.

Updated Aug 23, 2026
Search Tags:#debugging#investigation#root cause#systematic#error analysis
One-click install
npx skills add https://github.com/LillianLi110130/bu_agent_cli --skill systematic-debugging-lillianli110130
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/LillianLi110130/bu_agent_cli/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/LillianLi110130/bu_agent_cli --skill systematic-debugging-lillianli110130

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers and engineers efficiently identify the root cause of bugs and errors by following a structured, multi-phase debugging process, preventing superficial fixes.

Core Features & Use Cases

  • Structured Debugging Workflow: Guides through four key phases—investigation, pattern analysis, hypothesis testing, and implementation—to ensure thorough problem analysis.
  • Critical Rules Enforcement: Emphasizes finding the root cause prior to fixing, avoiding symptom patches, even under pressure or urgency.
  • Use Case: When facing complex bugs in production or flaky tests, users can systematically trace the bug origin, analyze patterns, formulate hypotheses, and implement verified fixes, significantly reducing rework and regressions.

Quick Start

Load the skill and follow the step-by-step instructions to investigate and fix bugs thoroughly.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging process for complex software bugs?▼

Systematic debugging is a structured process for root cause analysis that prevents superficial fixes by guiding developers through investigation, pattern analysis, hypothesis testing, and implementation.

How do I find the root cause of a flaky test in production?▼

To find the root cause of a flaky test, trace the bug origin by analyzing failure patterns, formulating hypotheses, and testing them before implementing verified fixes.

How do I stop developers from applying symptom patches during urgent bug fixes?▼

To stop symptom patches during urgent bug fixes, enforce critical rules requiring root cause identification prior to fixing, maintaining process discipline and comprehensive understanding under pressure.

Can I use this systematic debugging workflow for any software engineering error analysis?▼

Yes, you can use this systematic debugging workflow for any software engineering error analysis, as it is applicable in complex debugging scenarios to ensure thorough problem elimination with safety checks.

What are the limitations of systematic debugging for complex bugs?▼

A limitation of systematic debugging is the strict enforcement of finding the root cause prior to fixing, which may delay immediate symptom relief even under extreme urgency or pressure.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
JaimeJunrJaimeJunr
2

run-tests

Execute unit and integration tests, analyze failures, and re-run to verify corrections.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
I194I194
9

canary

Monitor deployed apps for console errors, performance regressions, and page failures.

Community
Advanced