skills.rest
lehoangphuc747
lehoangphuc747COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Apply a four-phase debugging workflow for root-cause analysis and verification.

Updated Jan 24, 2026
Search Tags:#debugging#isolation#verification#systematic#workflows#reproduction#root-cause-analysis
One-click install
npx skills add https://github.com/lehoangphuc747/anki-lms-demo --skill systematic-debugging-lehoangphuc747
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/lehoangphuc747/anki-lms-demo/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/lehoangphuc747/anki-lms-demo --skill systematic-debugging-lehoangphuc747

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This 4-phase debugging methodology prevents guesswork by guiding users through reproducibility, isolation, understanding, and verification to identify root causes.

Core Features & Use Cases

  • Reproduce: reliably recreate issues to establish a baseline.
  • Isolate: narrow down the responsible component or change.
  • Understand: perform a root-cause analysis using structured questions.
  • Fix & Verify: implement a fix and confirm it resolves the issue without introducing new problems.
  • Checklist: follow a comprehensive debugging checklist to maintain discipline.

Quick Start

Describe your issue, reproduce steps, and apply the 4-phase method to identify the root cause.

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 debugging complex software issues?▼

Systematic debugging is a structured, four-phase methodology for root-cause analysis that prevents guesswork by enforcing reproducibility, isolation, understanding, and verification across projects and environments.

How do I reliably reproduce and isolate a software bug?▼

To reproduce and isolate a bug, follow a structured workflow that first reliably recreates the issue to establish a baseline, then narrows down the responsible component or change to pinpoint the fault.

How do I perform root-cause analysis without guessing?▼

Root-cause analysis without guessing requires asking structured questions during the understanding phase to identify exactly why an issue occurs before implementing and verifying a fix.

What's the best way to verify a bug fix without introducing new problems?▼

The best way to verify a bug fix is to implement the correction and confirm it resolves the original issue without introducing regressions, using a comprehensive debugging checklist to maintain discipline.

Does this debugging methodology work across different projects and environments?▼

Yes, this debugging methodology works across different projects and environments because it enforces a clear, repeatable workflow with integration guidance for diverse debugging tasks.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
multiversxmultiversx
12

fix_verification

Verify smart contract bug fixes by running Mandos scenarios and regression tests.

Official
Intermediate
gqy20gqy20
4

debug-pipeline

Monitor AI pipeline stages and log anomalies to a Debug Issue Tracker.

Community
Advanced
eastreamseastreams
641

mcporter

Invoke MCP servers and tools from the command line with JSON output.

Official
Intermediate