skills.rest
wangx7
wangx7COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes before fixing bugs using a 4-phase workflow.

Updated Jun 26, 2026
Search Tags:#debugging#root cause analysis#bug fixing#systematic problem solving#test failure troubleshooting#symptom fix prevention#technical issue resolution
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill systematic-debugging-wangx7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/wangx7/skills-collection/tree/main/superpowers-main/skills/systematic-debugging
Command: npx skills add https://github.com/wangx7/skills-collection --skill systematic-debugging-wangx7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the wasted time, recurring bugs, and chaotic thrashing caused by random, symptom-focused fixes that fail to address underlying root causes, especially during time-sensitive emergencies or when facing pressure to deliver quick results.

Core Features & Use Cases

  • 4-Phase Structured Workflow: Mandatory root cause investigation, pattern analysis, hypothesis testing, and controlled implementation to ensure bugs are fixed permanently the first time.
  • Pressure-Resistant Guardrails: Anti-rationalization language, red flag checklists, and anti-pattern guidance to prevent shortcuts during emergencies, exhaustion, or when facing authority pressure from senior team members.
  • Supporting Techniques: Includes backward root cause tracing, defense-in-depth validation, and condition-based waiting patterns to handle complex multi-layer system bugs and flaky tests.
  • Use Cases: Ideal for test failures, production bugs, performance issues, build failures, and integration errors, particularly when previous fixes have failed or the issue seems deceptively simple.

Quick Start

Use the systematic-debugging skill to investigate the root cause of your current bug or test failure 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 bug instead of just fixing the symptom?▼

A systematic debugging approach prevents recurring bugs by enforcing root cause investigation before applying fixes. It provides a 4-phase structured workflow to eliminate wasted time and chaotic thrashing caused by symptom-focused random changes during time-sensitive emergencies.

What is the best way to troubleshoot recurring test failures and production bugs?▼

The best way to troubleshoot recurring test failures and production bugs is applying a 4-phase structured workflow with backward root cause tracing. This method ensures permanent bug resolution by enforcing pattern analysis and hypothesis testing before controlled implementation.

How do I stop making random code changes when fixing production bugs under time pressure?▼

To stop making random code changes under time pressure, use pressure-resistant guardrails including anti-rationalization language and red flag checklists. These tools prevent shortcuts and symptom-focused thrashing during emergencies, exhaustion, or authority pressure from senior team members.

How to debug flaky tests and complex multi-layer system integration errors?▼

Debug flaky tests and complex multi-layer system integration errors using backward root cause tracing and condition-based waiting patterns. These supporting techniques isolate intermittent failures and ensure defense-in-depth validation for permanent bug resolution across complex system layers.

When should I use a systematic problem solving approach for technical issue resolution?▼

Use systematic problem solving for technical issue resolution when facing test failures, performance degradation, build failures, or integration errors. It is particularly critical after multiple failed fix attempts or when the issue seems deceptively simple to prevent recurring bugs.

Related Skills

Explore More Software Engineering Skills→
rahmanayonrahmanayon

investigate

Plan root-cause investigations across investigate, analyze, hypothesize, and implement phases.

Community
Advanced
arthrodarthrod

systematic-debugging

Identify and resolve root causes of technical bugs through a four-phase framework.

Community
Advanced
cipherstashcipherstash
17

root-cause-tracing

Trace execution paths backward to identify root causes of deep errors.

Community
Basic
automatedigitalautomatedigital
1

systematic-debugging

Enforce root cause investigation before code changes in debugging workflows.

Official
Advanced