skills.rest
mrtolkien
mrtolkienCOMMUNITY
Explore all skills by this author →
Website𝕏@tolkicastsGitHub

systematic-debugging

Trace root causes of bugs through phased investigation and hypothesis testing.

5|Updated Feb 24, 2026
Search Tags:#defense-in-depth#root-cause#systematic-debugging#bug-investigation#evidence-collection#software-debugging#phase-based-process
One-click install
npx skills add https://github.com/mrtolkien/GHOST --skill systematic-debugging-mrtolkien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/mrtolkien/GHOST/tree/main/prompts/skills/superpowers/systematic-debugging
Command: npx skills add https://github.com/mrtolkien/GHOST --skill systematic-debugging-mrtolkien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined approach to find root causes before implementing fixes, reducing wasted effort and preventing regression.

Core Features & Use Cases

  • Four-phase root-cause investigation workflow (observe, pattern analyze, hypothesize, implement) to trace issues from symptom to source.
  • Evidence-gathering and instrumentation guidance to capture stack traces, data flow, and environmental context.
  • Effective for bugs, flaky tests, performance problems, and production incidents across multi-component systems.

Quick Start

Begin by reproducing the error, collecting diagnostics, and mapping data flow to locate the original trigger.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic approach to software debugging for complex multi-component systems?▼

Systematic software debugging uses a four-phase root-cause investigation workflow: observing symptoms, analyzing patterns, forming hypotheses, and implementing documented fixes to trace issues across multi-component systems.

How do I find the root cause of a flaky test or production incident?▼

To find the root cause of a flaky test, reproduce the error, gather diagnostic evidence like stack traces and data flow, and map the environmental context to locate the original trigger before implementing fixes.

What is the best way to collect evidence during a bug investigation?▼

The best way to collect evidence during a bug investigation is to apply instrumentation that captures stack traces, data flow mappings, and environmental context to support pattern analysis and hypothesis testing.

Does systematic debugging prevent regression when fixing performance problems?▼

Systematic debugging prevents regression by enforcing a disciplined root-cause investigation process that requires evidence gathering, hypothesis testing, and documented implementation before applying any code fixes.

Why does investigating bugs phase-by-phase reduce wasted effort?▼

Phase-based bug investigation reduces wasted effort by forcing developers to observe, pattern analyze, and hypothesize before implementing fixes, ensuring the actual root cause is addressed rather than just the symptoms.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced
danmestasdanmestas
4

systematic-debugging

Trace bugs to root causes via phase-based investigation and call stack analysis.

Community
Advanced
costrict-plugins-repocostrict-plugins-repo

systematic-debugging

Identify root causes through a four-phase debugging process before applying fixes.

Official
Advanced