skills.rest
sunLeee
sunLeeeCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide teams through a four-step debugging process to isolate root causes.

Updated Mar 19, 2026
Search Tags:#workflow#debugging#triage#root-cause#architecture-review#software-debugging
One-click install
npx skills add https://github.com/sunLeee/optimization --skill systematic-debugging-sunleee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/quality/check/systematic-debugging
Command: npx skills add https://github.com/sunLeee/optimization --skill systematic-debugging-sunleee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

시스템적 디버깅은 임의의 수정으로 인한 버그 재발을 방지하기 위해 근본 원인 조사를 우선시하는 절차를 제공합니다. 이를 통해 빠른 해결보다 견고한 수정과 재현 가능한 문제 해결을 보장합니다.

Core Features & Use Cases

  • 4단계 워크플로우: 근본 원인 조사, 패턴 분석, 가설 수립 및 검증, 구현(수정) 단계를 체계적으로 수행합니다.
  • 팀 정렬 및 거버넌스: 다중 구성 요소 간 일관된 디버깅 원칙과 협업 프로세스를 촉진합니다.
  • 적용 사례: 여러 서브시스템에 걸친 버그가 발생했을 때, 원인 파악과 수정 검증을 먼저 수행하여 배포 리스크를 낮춥니다.

Quick Start

에러를 간단히 서술하고 4단계 근본 원인 디버깅 프로세스를 시작해 문제를 식별하고 수정합니다.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
Why does software debugging fail when I apply quick fixes across multiple components?▼

Software debugging often fails with quick fixes because they mask the underlying issue. Systematic debugging prioritizes root-cause investigation to prevent bug recurrence and ensure robust, reproducible problem resolution.

What is the best way to isolate root causes before applying software patches?▼

The best way to isolate root causes is using a structured four-step debugging workflow: root-cause investigation, pattern analysis, hypothesis testing, and careful implementation with explicit checks.

How do I debug errors across multi-component systems without causing regressions?▼

Debug multi-component systems by following a disciplined workflow that includes reproducing the error, analyzing logs, testing hypotheses, and validating patches to lower deployment risk and prevent regressions.

When do I need a systematic debugging workflow instead of ad-hoc troubleshooting?▼

You need a systematic debugging workflow when bugs span multiple subsystems and require team alignment. It establishes consistent debugging principles and governance to reduce deployment risks before applying fixes.

How to start a root-cause investigation for a complex software bug?▼

Start a root-cause investigation by briefly describing the error message and reproduction steps, then initiating the four-step debugging process to identify the pattern and validate the fix.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
xiaobinxiaobin
1

systematic-debugging

Identifies and fixes bugs by tracing root causes across multi-component systems.

Community
Advanced
codenamevcodenamev
74

architecture-review

Coordinate multi-member architecture reviews and generate a consolidated findings document.

Community
Intermediate
AO-Cyber-SystemsAO-Cyber-Systems

df:quick

Execute ad-hoc tasks with atomic commits and STATE.md updates.

Official
Intermediate