skills.rest
tkhieu
tkhieuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Debugging

Diagnose software bug root causes through systematic four-phase debugging.

Updated Aug 23, 2026
Search Tags:#debugging#verification#systematic#root-cause#drill-down
One-click install
npx skills add https://github.com/tkhieu/peraichi-coding-agent-starter-kit --skill debugging-tkhieu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debugging
Source: https://github.com/tkhieu/peraichi-coding-agent-starter-kit/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/tkhieu/peraichi-coding-agent-starter-kit --skill debugging-tkhieu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic debugging framework to identify the true root cause before applying fixes, avoiding masking symptoms with quick, superficial patches.

Core Features & Use Cases

  • Systematic Debugging (Phase 1-4): Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation
  • Root Cause Tracing: Backtrace through call stacks to identify the original trigger
  • Defense-in-Depth: Add layered validation to prevent regressions
  • Verification: Enforce the Iron Law that no completion claims exist without fresh verification

Quick Start

Begin with Phase 1: read errors, reproduce, and gather evidence. Then progress through Phases 2-4 before implementing any fix. See guidance in:

  • references/systematic-debugging.md
  • references/root-cause-tracing.md
  • references/defense-in-depth.md
  • references/verification.md

Frequently Asked Questions about Debugging

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

FAQPage Schema
How do I systematically debug a software bug instead of just patching symptoms?▼

Systematic debugging traces root causes through four phases: reproduce and gather evidence, analyze patterns, test hypotheses, then implement fixes. This prevents masking symptoms with superficial patches and ensures lasting solutions.

Why does my test failure keep reappearing after I fix it?▼

Recurring failures often signal you've patched a symptom rather than the root cause. Backward call-stack tracing and defense-in-depth validation across entry, business logic, environment, and instrumentation layers reveal the original trigger.

How do I trace a bug back through the call stack to find where it started?▼

Root-cause tracing backtracks through your call stack to identify the original trigger point, not just where the error surfaced. This reveals the source of test failures, unexpected behavior, performance issues, and build failures.

What's the difference between fixing a bug and verifying it's actually fixed?▼

Verification enforces fresh evidence—rerunning tests, monitoring, and validation checks—to confirm the fix works across multiple layers. This prevents regressions and proves the original problem no longer exists.

Can I use systematic debugging for performance issues and integration problems?▼

Yes. The four-phase framework applies to test failures, unexpected behavior, performance issues, build failures, and integration problems. Each applies the same root-cause investigation and defense-in-depth validation approach.

Related Skills

Explore More Software Engineering Skills→
AdemKaoAdemKao

debug

Diagnose and fix codebase bugs through structured root-cause analysis.

Community
Intermediate
moberghrmoberghr
6

verification-before-completion

Require fresh execution evidence before reporting software tasks complete.

Official
Advanced
koralliskorallis
90

root-cause-tracing

Traces bugs backward through call stacks and execution flows to pinpoint their source.

Community
Advanced
NagyViktNagyVikt
2

systematic-debugging

Investigate software bugs through a four-phase root cause framework.

Community
Advanced