skills.rest
SteamedFish
SteamedFishCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

A structured 4-step method for debugging and root cause analysis.

6|Updated Jan 14, 2020
Search Tags:#debugging#root cause#troubleshooting#bug fixing#error analysis#systematic process
One-click install
npx skills add https://github.com/SteamedFish/dotfiles --skill systematic-debugging-steamedfish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/SteamedFish/dotfiles/tree/main/.config/opencode/skills/superpowers/systematic-debugging
Command: npx skills add https://github.com/SteamedFish/dotfiles --skill systematic-debugging-steamedfish

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 you always find the root cause of an issue before attempting any fixes, especially under pressure.

Core Features & Use Cases

  • Systematic Debugging: Guides you through a 4-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to systematically uncover the root cause of any bug.
  • Pressure Resistance: Includes rules and language designed to prevent shortcuts and rationalizations when under time pressure or facing complex issues.
  • Use Case: When a critical API is down, instead of guessing and applying quick fixes that might mask the real problem, you use this Skill to methodically investigate and fix the underlying issue, saving hours of debugging and preventing future occurrences.

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
How do I find the root cause of a bug instead of just fixing symptoms?▼

Root cause analysis requires a structured methodology to prevent wasted time and new bugs. This approach enforces a four-phase process of investigation, pattern analysis, hypothesis testing, and implementation to ensure the underlying issue is resolved.

What is a systematic process for troubleshooting software errors?▼

A systematic troubleshooting process guides developers through evidence gathering, data flow tracing, and hypothesis testing. This structured methodology ensures methodical investigation and resolution of software errors rather than relying on guesswork.

How do I avoid applying quick fixes when debugging under time pressure?▼

Debugging under pressure requires specific rules to resist shortcuts and rationalizations. This methodology includes pressure resistance language and structured phases to prevent symptom-fixing when facing complex issues or critical system outages.

What should I do when multiple bug fixes fail to resolve the issue?▼

When multiple fixes fail, architectural questioning and detailed data flow tracing are necessary. This systematic debugging approach provides specific steps to investigate deeper structural issues rather than applying repeated ineffective patches.

When do I need a structured methodology for bug fixing?▼

A structured bug fixing methodology is needed when guessing risks masking real problems or introducing new bugs. It is essential for complex software issues where finding the root cause before attempting fixes saves hours of debugging.

Does this systematic debugging approach work for critical API outages?▼

Yes, this systematic debugging methodology works for critical API outages by guiding methodical investigation of the underlying issue. It prevents guessing and quick fixes that might mask the real problem during high-pressure system failures.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
u9401066u9401066
1

bug-fix

Enforce a structured bug-fixing workflow with regression tests and root-cause analysis.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
primeBeriprimeBeri
1

Radberi-SystematicDebugging

Guide structured root cause analysis with four-phase debugging methodology.

Community
Advanced