skills.rest
yknothing
yknothingCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose and isolate root causes of bugs before implementing fixes.

1|Updated Mar 17, 2026
Search Tags:#debugging#regression#code-quality#root-cause#reproduction#bug-triage
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill systematic-debugging-yknothing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/yknothing/prodcraft/tree/main/skills/04-implementation/systematic-debugging
Command: npx skills add https://github.com/yknothing/prodcraft --skill systematic-debugging-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when a bug, failing test, regression, or unexpected behavior needs a root-cause-first debugging loop before code changes, especially when brownfield seams, recent releases, or historical defect matches make guesswork unsafe.

Core Features & Use Cases

  • Stepwise, evidence-based isolation of failure boundaries
  • Use history and context to guide root-cause hypothesis before patches
  • Outputs include bug-fix-report and course-correction-note for escalation when needed

Quick Start

Document the concrete failure boundary and reproduce it before gathering historical context.

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 failing test or runtime regression?▼

Isolate the root cause of a bug by documenting the concrete failure boundary and reproducing the issue before gathering historical context. This evidence-based approach ensures safe, smallest-change repairs.

What is the best way to debug unexpected behavior in a brownfield codebase?▼

The best way to debug unexpected behavior in a brownfield codebase is to apply stepwise, evidence-based isolation of failure boundaries. Reviewing recent releases and historical defect matches prevents unsafe guesswork before implementing fixes.

How do I ensure my bug fixes have minimal patch scope and regression protection?▼

Ensure minimal patch scope and regression protection by satisfying requirements for root-cause evidence. Diagnose and isolate the root cause first, guiding reproduction and boundary validation to ensure the smallest safe change.

When should I escalate a bug fix to address underlying architecture issues?▼

You should escalate a bug fix when architecture or planning issues are identified during root-cause isolation. The process outputs a course-correction-note for explicit escalation when the fix scope exceeds a simple patch.

Does this systematic debugging approach work for triaging recent release regressions?▼

Yes, this approach works for triaging recent release regressions by using history and context to guide root-cause hypotheses before patches. It applies across codebases and release scenarios to isolate failure boundaries.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
romiluz13romiluz13
161

root-cause-analysis

Guide root cause analysis through evidence collection and hypothesis testing.

Community
Basic
patrobpatrob

pw-bug-hunt

Run parallel hypotheses to isolate root causes and require failing tests before patching.

Community
Advanced