skills.rest
boazcstrike
boazcstrikeCOMMUNITY
Explore all skills by this author →
Website𝕏@boazcstrikeGitHub

systematic-debugging

Enforce a four-phase debugging process to identify root causes before fixes.

3|Updated Dec 23, 2025
Search Tags:#testing#debugging#troubleshooting#software development#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/boazcstrike/opencode --skill systematic-debugging-boazcstrike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/boazcstrike/opencode/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/boazcstrike/opencode --skill systematic-debugging-boazcstrike

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue of inefficient and ineffective debugging practices that lead to wasted time, recurring bugs, and architectural debt. It enforces a structured, scientific approach to problem-solving.

Core Features & Use Cases

  • Root Cause Analysis: Guides users to identify the fundamental reason for a bug before attempting any fix.
  • Systematic Investigation: Provides a phased approach (Investigation, Pattern Analysis, Hypothesis, Implementation) to ensure thoroughness.
  • Use Case: When a critical test fails in a CI/CD pipeline, this Skill ensures the engineer doesn't just "patch" the test but rigorously investigates the underlying code or environment issue, preventing future regressions.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the recent test failures.

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 recurring software bugs?▼

Root cause analysis for recurring bugs requires a systematic debugging process that investigates underlying issues before implementing fixes, preventing architectural decay and future regressions.

How do I systematically debug failing tests in a CI/CD pipeline?▼

Systematically debug failing tests by following a structured four-phase process: investigation, pattern analysis, hypothesis testing, and verification, ensuring you address the underlying code issue rather than patching the test.

How does a structured troubleshooting process prevent symptom-fixing?▼

A structured troubleshooting process prevents symptom-fixing by enforcing strict investigation and hypothesis testing phases, ensuring you identify and resolve the fundamental reason for a failure before writing code.

Can I use a systematic debugging approach for performance problems?▼

Yes, you can use systematic debugging for performance problems. The phased approach applies to all technical issues, guiding you through pattern analysis and hypothesis verification to isolate root causes.

What are the limitations of using a hypothesis testing method for bug fixing?▼

The limitation of hypothesis testing for bug fixing is the strict adherence required to the phased investigation process, which may slow down immediate patching but prevents architectural debt and recurring failures.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

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

Community
Advanced
kriscendobotkriscendobot
3

coverage-driven-testing

Increase test coverage and identify unreachable code in a monorepo.

Community
Advanced
89jobrien89jobrien
4

debugging

Parse logs and analyze stack traces to diagnose errors across languages.

Community
Advanced