skills.rest
kk20300113-png
kk20300113-pngCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes through a 4-phase debugging workflow.

Updated May 9, 2026
Search Tags:#software engineering#debugging#investigation#anti-patterns#root cause#bug fix#test failure
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill systematic-debugging-kk20300113-png
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/systematic-debugging
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill systematic-debugging-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random, symptom-focused bug fixes waste hours of development time, introduce new bugs, and fail to resolve underlying issues, especially under time pressure or after multiple failed quick fixes.

Core Features & Use Cases

  • 4-Phase Root Cause Workflow: Mandatory investigation, pattern analysis, hypothesis testing, and implementation steps to ensure fixes address source issues, not symptoms.
  • Pressure-Resistant Guardrails: Explicit "ALWAYS"/"NEVER" rules, anti-pattern guidance, and rationalization checklists to prevent shortcuts during emergencies or when exhausted.
  • Supporting Techniques: Built-in references for backward root cause tracing, condition-based waiting to eliminate flaky tests, and defense-in-depth validation to make bugs structurally impossible.
  • Use Case: Use for any test failure, production bug, performance issue, or integration error to avoid 2-3 hours of thrashing and achieve a 95% first-time fix rate.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the failing payment processing test before proposing any fixes.

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 test failure instead of just fixing symptoms?▼

To find the root cause of a test failure, apply a mandatory 4-phase investigation workflow involving pattern analysis, hypothesis testing, and implementation to ensure fixes address source issues rather than symptoms.

What is the best way to debug production bugs under extreme time pressure?▼

Debugging production bugs under time pressure requires pressure-resistant guardrails, utilizing explicit ALWAYS/NEVER rules and rationalization checklists to prevent shortcuts and avoid hours of wasted thrashing.

Why does my random bug fix keep failing to resolve recurring performance degradation?▼

Random symptom-focused fixes fail to resolve performance degradation because they do not address the underlying issue, often introducing new bugs; a systematic root cause investigation is required to achieve a 95% first-time fix rate.

How do I stop flaky tests using condition-based waiting during debugging?▼

Stop flaky tests during debugging by applying condition-based waiting techniques, which eliminate timing inconsistencies by ensuring backward root cause tracing validates exact execution states before proceeding.

When should I not use quick fixes for integration errors?▼

You should never use quick fixes for integration errors after multiple failed attempts, as symptom-focused patches waste development time; instead, enforce a systematic root cause investigation workflow with anti-pattern guidance.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
danilonovaisvdanilonovaisv
1

systematic-debugging

Guide engineers through a four-phase debugging workflow for root-cause investigation.

Community
Advanced
lv7devlv7dev

Root Cause Tracing

Trace call stacks backward to identify original bug triggers.

Community
Advanced
alffeialffei
69

systematic-debugging

Diagnose software bugs through a four-phase root cause investigation process.

Community
Advanced