skills.rest
benthamite
benthamiteCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide a four-phase debugging process to identify and resolve root causes.

9|1|Updated Jul 19, 2022
Search Tags:#debugging#root cause#troubleshooting#bug fixing#error resolution#systematic process
One-click install
npx skills add https://github.com/benthamite/dotfiles --skill systematic-debugging-benthamite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/benthamite/dotfiles/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/benthamite/dotfiles --skill systematic-debugging-benthamite

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a robust framework to systematically debug any technical issue, ensuring you find the root cause rather than just fixing symptoms, which saves time and prevents recurring problems.

Core Features & Use Cases

  • Four-Phase Process: Guides users through Investigation, Pattern Analysis, Hypothesis, and Implementation.
  • Root Cause Mandate: Emphasizes finding the fundamental issue before applying any fix.
  • Pressure Resistance: Includes explicit rules and language to prevent shortcuts under time pressure.
  • Use Case: When a critical API endpoint starts returning errors, use this Skill to methodically trace the issue from the error message back to the originating code, rather than applying a quick, temporary patch.

Quick Start

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

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 process for finding the root cause of software bugs?▼

A systematic debugging process uses a structured four-phase approach to find the root cause of software bugs, moving through investigation, pattern analysis, hypothesis formation, and implementation to prevent symptom-fixing.

How do I troubleshoot complex system errors without taking shortcuts under pressure?▼

To troubleshoot complex system errors under pressure, follow a systematic debugging process with explicit rules that mandate evidence gathering and data flow tracing, preventing quick temporary patches and shortcuts during critical incidents.

How do I trace data flow to investigate a critical API endpoint returning errors?▼

Trace data flow by gathering evidence during the investigation phase, methodically tracking the issue from the API error message back to the originating code, ensuring you identify the fundamental issue before applying any fix.

Why do my bug fixes only address symptoms instead of resolving the underlying issue?▼

Bug fixes often address symptoms because of shortcuts taken under time pressure; a systematic debugging process enforces a root cause mandate, requiring pattern analysis and hypothesis formation before implementation to prevent recurring problems.

When should I use a structured hypothesis formation approach for troubleshooting?▼

You should use a structured hypothesis formation approach for troubleshooting any technical issue in complex systems, ensuring you analyze patterns and gather evidence before implementation to avoid applying temporary patches.

Related Skills

Explore More Software Engineering Skills→
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
cyberkaidacyberkaida
797

ctf-rev

Analyze CTF binaries to extract flags through structured reverse engineering.

Community
Advanced
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced