skills.rest
namhoangg
namhoanggCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a four-phase root-cause workflow before implementing bug fixes.

Updated Aug 23, 2026
Search Tags:#testing#debugging#defense-in-depth#systematic#workflows#root-cause#phase-based
One-click install
npx skills add https://github.com/namhoangg/agent-starter-kit --skill systematic-debugging-namhoangg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/namhoangg/agent-starter-kit/tree/main/cursor/skills/systematic-debugging
Command: npx skills add https://github.com/namhoangg/agent-starter-kit --skill systematic-debugging-namhoangg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging standardizes how teams approach hard bugs to avoid rushing to fixes and to ensure root-cause investigation.

Core Features & Use Cases

  • Phase-based workflow (Phase 1–4) guiding root-cause investigation before fixes.
  • Defense-in-depth and anti-patterns to prevent symptom fixes.
  • Reference materials and real-world examples to train teams on debugging best practices.

Quick Start

Clone the repository, open SKILL.md, and start applying the four-phase systematic-debugging workflow to any bug.

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 workflow for root-cause investigation?▼

Systematic debugging is a structured root-cause investigation workflow that enforces completing four distinct phases before implementing fixes to prevent symptom patches and resolve hard bugs safely.

How do I debug software bugs without just fixing symptoms?▼

Apply a phase-based workflow requiring you to complete Phase 1 through Phase 4 root-cause investigation before implementing fixes, using defense-in-depth and anti-pattern guidance to prevent symptom fixes.

When should I use a structured debugging workflow for test failures?▼

Use a structured debugging workflow for any software engineering task involving a bug, test failure, or unexpected behavior across projects and codebases to ensure thorough root-cause investigation before fixing.

What is the best way to approach unexpected behavior across different codebases?▼

The best way to approach unexpected behavior is standardizing root-cause investigation through a four-phase systematic debugging workflow, ensuring teams avoid rushing to fixes and address the actual underlying issue.

Does systematic debugging require any specific testing frameworks or dependencies?▼

No, systematic debugging requires no specific testing frameworks or dependencies. It applies to any software engineering project or codebase experiencing bugs, test failures, or unexpected behavior.

Why does my bug fix keep causing new issues in other parts of the system?▼

Your bug fix likely addressed a symptom rather than the root cause. Systematic debugging applies anti-patterns and defense-in-depth guidance during a four-phase investigation to prevent incomplete symptom fixes.

Related Skills

Explore More Software Engineering Skills→
mrkhachaturovmrkhachaturov

systematic-debugging

Guide engineers through phased root-cause investigation and evidence-based debugging.

Community
Advanced
shekerkammashekerkamma

investigate

Systematically debugs software errors by tracing root causes before implementing fixes.

Community
Advanced
UniClipboardUniClipboard
1.5k

systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation process.

Official
Advanced
farsinkfarsink

systematic-debugging

Guide software debugging through a four-phase root cause analysis process.

Community
Advanced