skills.rest
johan-Rm
johan-RmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Breaks down bug-finding into a structured four-step process for engineers.

Updated May 6, 2026
Search Tags:#testing#debugging#troubleshooting#root cause analysis#software quality#reliability
One-click install
npx skills add https://github.com/johan-Rm/agents --skill systematic-debugging-johan-rm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/johan-Rm/agents/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/johan-Rm/agents --skill systematic-debugging-johan-rm

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the issue of inefficient, guess-based debugging that leads to flaky fixes, recurring issues, and wasted development time.

Core Features & Use Cases

  • Root Cause Analysis: Provides a structured four-phase framework to identify the underlying cause before applying any fixes.
  • Defense-in-Depth: Offers patterns for multi-layer validation to make bugs structurally impossible.
  • Reliable Testing: Includes utilities for condition-based waiting to replace brittle, arbitrary timeouts in test suites.
  • Use Case: When a test fails intermittently in CI, use this skill to trace the data flow, identify the race condition, and implement a robust wait condition that ensures 100% test reliability.

Quick Start

Initiate the systematic debugging process to investigate the current test failure by tracing the data flow and identifying the root cause.

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 intermittent test failures in CI?▼

A systematic debugging process enforces root cause investigation before applying fixes, utilizing a structured four-phase framework to trace data flow, analyze patterns, and identify underlying causes in complex software systems.

What is the best way to debug production bugs without guessing?▼

The best way to debug production bugs without guessing is to apply a four-phase scientific framework that enforces systematic tracing and pattern analysis to pinpoint the exact defect before implementation.

How can I make software bugs structurally impossible to prevent recurring issues?▼

You can make software bugs structurally impossible by applying defense-in-depth patterns that enforce multi-layer validation techniques, ensuring architectural integrity and preventing flaky fixes from recurring.

Does this systematic debugging approach work for performance issues and complex software systems?▼

Yes, this systematic debugging approach works for performance issues and complex software systems by applying rigorous root cause analysis and multi-layer validation to ensure defects are resolved without architectural compromise.

Why should I use a scientific debugging process instead of applying quick fixes?▼

You should use a scientific debugging process instead of quick fixes because guess-based debugging leads to flaky fixes, recurring issues, and wasted development time, whereas systematic tracing ensures permanent resolution.

Related Skills

Explore More Software Engineering Skills→
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced
duongbui234duongbui234

systematic-debugging

Systematizes software debugging via Investigation, Analysis, Hypothesis, Implementation phases.

Community
Advanced
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
uv-xiaouv-xiao
1

uv-systematic-debugging

Guide four-phase debugging through investigation, pattern analysis, hypothesis, and implementation.

Community
Advanced