skills.rest
KanuToCL
KanuToCLCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide four-phase debugging to identify root causes of technical issues.

Updated Jan 19, 2026
Search Tags:#debugging#root cause#troubleshooting#bug fixing#error analysis#systematic process
One-click install
npx skills add https://github.com/KanuToCL/SonoTag --skill systematic-debugging-kanutocl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/KanuToCL/SonoTag/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/KanuToCL/SonoTag --skill systematic-debugging-kanutocl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, four-phase process to systematically identify and resolve the root cause of any bug, test failure, or unexpected behavior, preventing the common pitfalls of quick fixes and symptom-based solutions.

Core Features & Use Cases

  • Mandatory Root Cause Analysis: Enforces a strict "no fixes without investigation" policy.
  • Four-Phase Framework: Guides users through Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Pressure Resistance: Includes specific rules and language to counteract time pressure and rationalization.
  • Use Case: When a critical production bug appears, this Skill ensures that the team doesn't just apply a band-aid, but rigorously follows a process to find and fix the underlying issue, preventing recurrence.

Quick Start

Use the systematic-debugging skill to debug any encountered bug or unexpected behavior.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic process for debugging technical issues to find the root cause?▼

A systematic debugging process enforces a strict no-fixes-without-investigation policy, guiding users through four phases: Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation to identify root causes.

How do I fix a critical production bug without just applying a band-aid?▼

To fix a critical production bug without a band-aid, follow a four-phase debugging framework that mandates thorough investigation and pattern analysis before implementing any controlled fixes to resolve the underlying issue.

How do I resist time pressure and rationalization when troubleshooting unexpected behavior?▼

To resist time pressure during troubleshooting, apply specific pressure-resistance rules embedded in the debugging framework that enforce hypothesis formation and controlled implementation instead of quick symptom fixes.

What is the best way to analyze error patterns and form testing hypotheses for bug fixing?▼

The best way to analyze error patterns is using a structured debugging framework that separates Pattern Analysis and Hypothesis & Testing into distinct phases, ensuring controlled verification before implementation.

Can I use tracing and TDD skills for deep-dive analysis during root cause identification?▼

Yes, the systematic debugging process integrates directly with tracing and TDD skills to perform deep-dive analysis and verify controlled implementation during the hypothesis and testing phase.

Related Skills

Explore More Software Engineering Skills→
AstrumonAstrumon

debugging-wizard

Diagnose Kotlin/JVM bugs, coroutine deadlocks, and runtime errors with stack traces.

Community
Advanced
xxthunderxxthunder
1

retrospective

Document user dissatisfaction and update development guidelines to prevent recurrence.

Community
Intermediate
sogadaikisogadaiki

investigate

Explore codebases with parallel sub-agents using glob and grep operations.

Community
Intermediate
obraobra
269.6k

systematic-debugging

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

Community
Intermediate