skills.rest
BumpyClock
BumpyClockCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of bugs and failures before proposing fixes.

1|1|Updated Jun 2, 2025
Search Tags:#debugging#defense-in-depth#trace#phases#root-cause#systematic-debugging
One-click install
npx skills add https://github.com/BumpyClock/dotfiles --skill systematic-debugging-bumpyclock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/BumpyClock/dotfiles/tree/main/.ai_agents/skills/systematic-debugging
Command: npx skills add https://github.com/BumpyClock/dotfiles --skill systematic-debugging-bumpyclock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers identify root causes of bugs and failures before proposing fixes, preventing symptom-focused patches.

Core Features & Use Cases

  • Enforces a four-phase debugging process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) and stage gates (Phase 1 before fixes)
  • Provides defense-in-depth guidance to validate data and trace root causes across layers
  • Applies to bugs, test failures, performance issues, integrations, and production incidents with structured reproduction and validation

Quick Start

Follow the four phases of the skill to systematically investigate and resolve issues before patching, with explicit steps and guardrails.

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 a root cause before patching a production bug?▼

To find a root cause before patching, use a systematic debugging process that enforces a mandatory root cause investigation phase before any fixes are proposed. This prevents symptom-focused patches and validates issues across layers.

How do I debug test failures systematically?▼

Debug test failures systematically by following a four-phase process: root cause investigation, pattern analysis, hypothesis and testing, and implementation. Phase 1 must be completed before applying any fixes to ensure accurate resolution.

Can I use systematic debugging for performance problems and integration issues?▼

Yes, systematic debugging applies to performance problems and integration issues across software projects. It provides structured reproduction and validation alongside defense-in-depth guidance to trace root causes accurately.

Why do my bug fixes keep causing new failures?▼

Bug fixes often cause new failures because they address symptoms rather than root causes. A systematic debugging approach enforces pattern analysis and hypothesis testing before implementation, preventing patches that mask underlying issues.

Does systematic debugging require specific dependencies or test frameworks?▼

Systematic debugging requires no specific dependencies or test frameworks. It is applicable to any technical issue across software projects, using a four-phase methodology and defense-in-depth guidance to validate data without external tools.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

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

Official
Intermediate
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
tsuji-tomonoritsuji-tomonori

a11y-ci-gating

Automate accessibility testing in CI/CD pipelines with quality gates.

Community
Advanced
romiluz13romiluz13
161

debugging-patterns

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Advanced