skills.rest
circld
circldCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase debugging to identify root causes before fixes.

1|Updated May 25, 2025
Search Tags:#debugging#troubleshooting#error handling#root cause analysis#bug fixing#systematic process
One-click install
npx skills add https://github.com/circld/dotfiles --skill systematic-debugging-circld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/circld/dotfiles/tree/main/external/opencode/skills/systematic-debugging
Command: npx skills add https://github.com/circld/dotfiles --skill systematic-debugging-circld

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring that the root cause of any technical issue is identified and addressed before any fixes are implemented.

Core Features & Use Cases

  • Systematic Investigation: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to uncover the true source of bugs.
  • Pressure Resistance: Provides explicit rules and language to counteract the temptation to apply quick fixes under time pressure or when a simple solution seems obvious.
  • Use Case: When a test fails or an application behaves unexpectedly, use this Skill to systematically diagnose the problem, ensuring that only the root cause is fixed, leading to more stable and reliable software.

Quick Start

Use the systematic debugging skill to investigate any unexpected behavior 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 the symptoms?▼

Systematic debugging uses a four-phase process—Investigation, Pattern Analysis, Hypothesis, and Implementation—to uncover the true source of test failures. It enforces thorough investigation and verification to prevent wasted time fixing symptoms instead of root causes.

What is the best way to debug software when under tight time pressure?▼

Systematic debugging provides explicit rules to resist pressure and avoid fixing symptoms when a simple solution seems obvious. It enforces pattern analysis and hypothesis testing to ensure only the root cause is addressed, preventing new bugs under tight deadlines.

How do I systematically troubleshoot unexpected application behavior and test failures?▼

You systematically troubleshoot test failures by moving through four mandatory phases: Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured process ensures you verify the root cause of unexpected behavior before writing any fix code.

Why should I use a systematic debugging process for fixing software bugs?▼

A systematic debugging process prevents wasted time and new bugs by ensuring the root cause of technical issues is identified before fixes are implemented. It enforces pattern analysis and hypothesis testing to address the true source of software bugs.

Related Skills

Explore More Software Engineering Skills→
0xHarbs0xHarbs
1

debug

Diagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
shiaho777shiaho777
5.5k

debug

Diagnose and fix software bugs through a reproducible debugging workflow.

Community
Intermediate
iciakkyiciakky

debug

Diagnoses root causes of code modifications using a seven-step debugging workflow and generates verified fix plans.

Community
Intermediate