skills.rest
jonathanmalkin
jonathanmalkinCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase debugging with root cause analysis and hypothesis testing.

61|9|Updated Mar 9, 2026
Search Tags:#testing#debugging#systematic approach#troubleshooting#root cause analysis#bug fixing
One-click install
npx skills add https://github.com/jonathanmalkin/jules --skill systematic-debugging-jonathanmalkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/jonathanmalkin/jules/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/jonathanmalkin/jules --skill systematic-debugging-jonathanmalkin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents wasted time and new bugs by enforcing a rigorous, systematic approach to debugging, ensuring that the root cause of any technical issue is identified and addressed before any fixes are attempted.

Core Features & Use Cases

  • Root Cause Investigation: Guides users through error messages, reproduction steps, and evidence gathering.
  • Pattern Analysis: Helps identify underlying patterns and compare against working examples or references.
  • Hypothesis Testing: Promotes a scientific method for proposing and testing minimal fixes.
  • Use Case: When a critical test fails in CI, this Skill ensures the engineer doesn't just "quick fix" it, but systematically traces the data flow, identifies the exact point of failure, and implements a robust solution, preventing recurrence.

Quick Start

Use the systematic-debugging skill to investigate and fix the intermittent test failure in the CI pipeline.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a systematic approach to debugging software bugs?▼

A systematic debugging approach uses a structured four-phase process to identify root causes, analyze patterns, test hypotheses, and carefully implement fixes to prevent symptom-based patches.

How do I find the root cause of a test failure in my CI pipeline?▼

To find the root cause of a test failure, trace data flow across components, gather reproduction evidence, compare against working references, and propose minimal hypothesis tests before implementing a fix.

How do I troubleshoot production bugs without introducing new issues?▼

Troubleshoot production bugs by systematically gathering error evidence, identifying underlying patterns, and testing minimal fixes to avoid architectural misunderstandings and prevent recurrence.

What is the best way to fix performance problems in multi-component systems?▼

The best way to fix multi-component performance problems is applying a rigorous debugging process that emphasizes root cause analysis and pattern identification over quick symptom-based fixes.

Can I use a structured debugging process for build issues?▼

Yes, a structured debugging process supports troubleshooting build issues by guiding you through error message investigation, evidence gathering, and hypothesis testing across multi-component systems.

Why should I not apply a quick fix to an intermittent technical issue?▼

Quick fixes often address symptoms rather than root causes, leading to wasted time and new bugs; a systematic approach ensures the exact point of failure is identified and resolved robustly.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

debug

Run structured debugging sessions to reproduce, isolate, and diagnose software errors.

Official
Intermediate
CyapstayeCyapstaye
9

systematic-debugging

Execute a four-phase debugging workflow to identify and resolve technical root causes.

Community
Advanced
sast-playgroundsast-playground

dashboard-testing

Test Aspire Dashboard models and Blazor components with xUnit and bUnit.

Official
Intermediate
csuzngjhcsuzngjh
1

inject-rule

Appends user-provided rule arguments to the Ad-hoc Rules section of USER_CONTEXT.md.

Community
Basic