skills.rest
cabezno
cabeznoCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce an evidence-first workflow for root-cause debugging across multi-component systems.

Updated May 15, 2026
Search Tags:#testing#debugging#troubleshooting#root cause analysis#incident response#regression testing#data flow tracing
One-click install
npx skills add https://github.com/cabezno/bmb-encover-agent --skill systematic-debugging-cabezno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill systematic-debugging-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Systematic debugging prevents wasted time and recurring failures by forcing a disciplined root-cause investigation before applying any code changes.

Core Features & Use Cases

  • Four-phase debugging workflow: Investigation, pattern analysis, hypothesis + minimal testing, then verified implementation.
  • Evidence-first isolation: Reproduce consistently, review recent changes, trace data flow across components, and form a defensible root-cause hypothesis.
  • Regression-proof fixes: Create a failing test case, implement a single fix, and verify no regressions (including a safety rule for repeated failures).

Use case example: When a CI build starts failing for a production service, use this Skill to read the full error/stack trace, trace where the faulty value originates, isolate the failing component, and then implement the smallest root-cause fix backed by a regression test.

Quick Start

Use systematic-debugging to debug a failing test run by providing the exact error output and the repository path, then request a Phase 1 root-cause investigation plan before any fixes are proposed.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is root cause debugging and how does an evidence-first workflow prevent recurring production bugs?▼

Root cause debugging is a disciplined workflow that blocks code fixes until a reliable reproduction and data flow trace isolate the true origin of production bugs, preventing wasted time and recurring failures.

How do I troubleshoot a failing CI build by tracing data flow across multi-component systems?▼

To troubleshoot a failing CI build, start by reading the full error stack trace, trace where faulty values originate across components, form a single root-cause hypothesis, and verify minimally before implementing the fix.

How do I create a regression test that proves a bug fix before implementing the code change?▼

To create a regression-proof fix, write a failing test case that reliably reproduces the bug, implement the smallest root-cause code change, and then verify the test passes without introducing new regressions.

What is the best way to stop repeated test failures from regressing after applying a patch?▼

The best way to stop repeated test failures is to apply a safety rule for repeated failures: enforce a four-phase investigation, add a failing regression test first, and verify no regressions after the minimal fix.

Does systematic debugging work for integration issues and build failures in complex environments?▼

Yes, systematic debugging applies to build and integration issues by requiring you to reproduce consistently, review recent changes, trace data flow across components, and form a defensible hypothesis before fixing.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

extract-test-failures

Parse test logs to extract and categorize failures by type.

Community
Basic
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
peshaypeshay
1

bmad-investigate

Grade evidence and reconstruct scenarios into structured case files.

Community
Advanced
saknarinZsaknarinZ

Debugging

Diagnose software defects through structured reproduction, isolation, and verification.

Community
Advanced