skills.rest
robkisk
robkiskCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase debugging to identify and fix root causes.

Updated Mar 10, 2026
Search Tags:#debugging#investigation#root cause#troubleshooting#error handling#bug fixing
One-click install
npx skills add https://github.com/robkisk/coding-agents-databricks-app --skill systematic-debugging-robkisk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/robkisk/coding-agents-databricks-app/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/robkisk/coding-agents-databricks-app --skill systematic-debugging-robkisk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring that the root cause of any issue is identified and fixed, rather than just patching symptoms.

Core Features & Use Cases

  • Structured Investigation: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to systematically uncover the origin of bugs.
  • Pressure Resistance: Includes specific rules and language designed to counteract common rationalizations made under time pressure or when a quick fix seems obvious.
  • Use Case: When a critical API endpoint starts returning errors, instead of immediately trying a quick fix like adding a retry mechanism, this Skill forces a thorough investigation to understand why the errors are occurring, preventing recurring issues and more complex failures down the line.

Quick Start

Use the systematic-debugging skill to investigate any bug or unexpected behavior you encounter.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is the best way to find the root cause of a software bug instead of just patching symptoms?▼

Root cause debugging requires a structured investigation process that gathers evidence, traces data flow, and tests hypotheses before implementation. This prevents wasted time and recurring issues by ensuring the actual origin of unexpected behavior is fixed.

How do I systematically troubleshoot an API endpoint that starts returning unexpected errors?▼

Systematic troubleshooting of API errors involves a four-phase process: investigation, pattern analysis, hypothesis testing, and verified implementation. This approach resists the urge to apply quick fixes like retries, ensuring the underlying failure is resolved.

Why do quick fixes for software bugs often lead to more complex failures down the line?▼

Quick fixes often lead to complex failures because they patch symptoms rather than the root cause. Without systematic investigation and pattern analysis, the underlying issue remains, causing recurring errors and potentially introducing new bugs into the system.

How to investigate a bug under time pressure without missing the actual origin of the failure?▼

Investigating bugs under time pressure requires specific rules that counteract rationalizations for quick fixes. A structured four-phase process mandates evidence gathering and data flow tracing to ensure the root cause is identified before implementation.

When do I need a structured investigation process for troubleshooting unexpected software behavior?▼

A structured investigation process is needed whenever you encounter unexpected behavior in complex systems. It mandates evidence gathering and data flow tracing to identify the root cause, preventing the recurrence of issues caused by symptom-fixing.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
shekerkammashekerkamma

investigate

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

Community
Advanced
aarushlohitaarushlohit

error-handler

Develop error handling strategies with typed errors, retry logic, and observability.

Community
Intermediate
riddopicriddopic

systematic-debugging

Guide users through a four-phase structured debugging process to resolve software bugs and test failures.

Community
Advanced