skills.rest
devon87warren-afk
devon87warren-afkCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide 4-phase debugging with reproduction, isolation, understanding, and verification.

Updated Mar 7, 2026
Search Tags:#debugging#problem solving#troubleshooting#software development#root cause analysis#verification
One-click install
npx skills add https://github.com/devon87warren-afk/eboss-monorepo --skill systematic-debugging-devon87warren-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/devon87warren-afk/eboss-monorepo/tree/main/apps/manager/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/devon87warren-afk/eboss-monorepo --skill systematic-debugging-devon87warren-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, four-phase methodology to debug complex issues, moving beyond guesswork to ensure root causes are identified and problems are verifiably resolved.

Core Features & Use Cases

  • Structured Debugging: Follows a 4-phase process: Reproduce, Isolate, Understand, and Fix & Verify.
  • Root Cause Analysis: Employs techniques like the "5 Whys" to uncover the fundamental source of a problem.
  • Evidence-Based Verification: Ensures fixes are thoroughly tested and regressions are prevented.
  • Use Case: When encountering a persistent, hard-to-reproduce bug in a production system, use this skill to systematically narrow down the possibilities and confirm the fix.

Quick Start

Use the systematic-debugging skill to help reproduce and isolate a bug that started occurring after the last deployment.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging methodology for complex technical issues?▼

Systematic debugging is a structured methodology that moves beyond guesswork to ensure root causes are identified and problems are verifiably resolved through reproduction, isolation, understanding, and verification.

How do I reproduce and isolate a hard-to-reproduce bug in a production system?▼

To reproduce and isolate a bug, follow a structured debugging workflow that systematically narrows down possibilities using common command-line tools for investigation and evidence gathering.

How do I perform root cause analysis using the 5 Whys technique?▼

Root cause analysis employs the 5 Whys technique during the understanding phase to uncover the fundamental source of a problem, ensuring you address the underlying issue rather than surface symptoms.

What is the best way to verify a software fix and prevent regressions?▼

The best way to verify a fix is through evidence-based verification, ensuring the fix is thoroughly tested during the final phase of the debugging process to prevent future regressions.

Do I need specific command-line tools to troubleshoot software development issues systematically?▼

The methodology supports debugging workflows by utilizing common command-line tools for investigation, meaning standard command-line utilities are sufficient for guiding users through the troubleshooting phases.

Related Skills

Explore More Software Engineering Skills→
cxm6467cxm6467

setup-slack

Automates installation and configuration of the slk CLI for Slack integration.

Community
Intermediate
GenEducationGenEducation

land-and-deploy

Merge a pull request, wait for CI and deployment, and verify production health with canary checks.

Official
Advanced
PROdotesPROdotes

Scientific Debugging (QA & Testing)

Automate Python-based debugging workflows covering reproduction through verification.

Community
Advanced
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced