skills.rest
emelleby
emellebyCOMMUNITY
Explore all skills by this author →
Website𝕏@emellebyGitHub

systematic-debugging

Identify software issue root causes through a 4-phase debugging methodology.

Updated Jan 22, 2026
Search Tags:#debugging#verification#systematic#phases#reproduction#evidence-based#root-cause-analysis
One-click install
npx skills add https://github.com/emelleby/tc-vsme --skill systematic-debugging-emelleby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/emelleby/tc-vsme/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/emelleby/tc-vsme --skill systematic-debugging-emelleby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, repeatable approach to debugging that emphasizes reproducing the issue, isolating its cause, understanding the root reason, and verifying a fix with evidence.

Core Features & Use Cases

  • 4-Phase Debugging Process: Reproduce, Isolate, Understand, and Fix & Verify to prevent guessing.
  • Root Cause Documentation: Structured questions and analysis steps to surface the true cause.
  • Evidence-Based Validation: Verification checks ensure functionality is restored without introducing new issues.
  • Use Case: When debugging a complex bug that spans multiple modules or environments, follow the phases to converge on the root cause.

Quick Start

Start a debugging session by outlining the issue, listing reproduction steps, and proceeding through the four phases to identify the root cause and confirm the fix.

Frequently Asked Questions about systematic-debugging

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

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

Systematic debugging is a disciplined methodology to identify root causes of software issues. Use it for complex debugging scenarios spanning multiple modules or environments where guessing is unproductive.

How do I find the root cause of a bug across multiple services?▼

To find the root cause of a bug, follow a 4-phase methodology: reproduce the issue, isolate the cause, understand the root reason, and verify the fix with collected evidence to ensure the underlying problem is addressed.

What are the steps for evidence-based debugging?▼

Evidence-based debugging requires structured documentation across four phases: reproducing the issue, isolating the cause, understanding the root reason, and verifying functionality is restored without introducing new issues.

How do I verify a software fix without introducing new issues?▼

Verify a software fix by applying evidence-based validation checks during the final debugging phase to ensure functionality is fully restored and confirm the correction does not introduce new issues.

Does systematic debugging work for complex issues in any codebase?▼

Systematic debugging applies to complex scenarios across codebases, services, and environments without requiring specific dependencies, providing a repeatable approach to converge on the true root cause.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
dobrinz123dobrinz123

gsd-verify-work

Run conversational user acceptance tests and output a {phase_num}-UAT.md report.

Community
Advanced
thesaifalitaithesaifalitai
8

debugging-wizard

Diagnose and isolate software issue root causes through structured debugging workflows.

Community
Advanced
writerwriter
6

Returns Root Cause Analysis

Analyzes transportation and logistics data to identify risks and recommend optimizations.

Official
Advanced