skills.rest
jsloat
jsloatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnoses root causes of software bugs through four-phase investigation.

5|Updated Feb 10, 2026
Search Tags:#debugging#reproducibility#root-cause#error-analysis#systematic-debugging#bug-triage#phased-workflow
One-click install
npx skills add https://github.com/jsloat/superpowers-for-copilot --skill systematic-debugging-jsloat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jsloat/superpowers-for-copilot/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/jsloat/superpowers-for-copilot --skill systematic-debugging-jsloat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers to perform disciplined root-cause analysis before proposing any fix, reducing guesswork and regressive patches.

Core Features & Use Cases

  • Four-phase debugging workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation.
  • Emphasis on reproducibility, evidence gathering, and validation across code paths and components.
  • Applicable to test failures, production bugs, build errors, and integration problems, especially under time pressure.

Quick Start

Describe the issue, reproduce it consistently, then trace data flow through each phase before suggesting changes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic root-cause debugging and when should I use it?▼

Systematic root-cause debugging identifies the origin of software failures before applying fixes. Use it for test failures, production bugs, build errors, and integration problems to prevent regressive patches and symptom fixes.

How do I trace a bug root cause before applying a fix?▼

To trace a bug root cause, follow a four-phase workflow: investigate the issue, analyze patterns, test hypotheses, and implement the fix. This requires consistent reproduction, explicit data collection, and validation at each stage.

What's the best way to debug intermittent production bugs under time pressure?▼

The best way to debug production bugs under time pressure is disciplined phase execution: gather evidence, check reproducibility, analyze data flow patterns, and validate hypotheses before modifying code to avoid guesswork.

Does root-cause debugging work for build failures and integration problems?▼

Yes, root-cause debugging works across software issues including build failures and integration problems. It guides you through evidence gathering and hypothesis testing across code paths and components to find the true origin.

Why do my bug fixes keep causing regressions in other tests?▼

Bug fixes cause regressions when they address symptoms rather than root causes. Systematic debugging prevents this by requiring hypothesis testing and evidence validation across data flows before implementing any code changes.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
drimchanskydrimchansky

debug

Guide systematic reproduction, isolation, diagnosis, and verification of software bugs.

Community
Intermediate