systematic-debugging

Diagnose bugs through a structured root-cause analysis workflow.

75|18|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/JKHeadley/instar --skill systematic-debugging-jkheadley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/JKHeadley/instar/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/JKHeadley/instar --skill systematic-debugging-jkheadley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents blind probing when something breaks by forcing a disciplined debugging workflow that identifies the exact failure, the expected behavior, and the true root cause before any fix is attempted.

Core Features & Use Cases

  • 4-Phase Debugging Process: Guides investigation through identification, isolation, fixing, and verification so the real issue is understood first.
  • Evidence-Driven Analysis: Encourages reproducing failures, tracing execution paths, and confirming hypotheses with logs, tests, or debugger output.
  • Safe Fixing Discipline: Promotes minimal changes, test-first validation, and full regression checks to avoid introducing new bugs.
  • Use Case: A test suddenly starts failing after a recent change, and this Skill helps you reproduce the failure, locate the divergence point, apply the smallest correct fix, and verify the result end to end.

Quick Start

Use this skill to investigate the failing behavior by reproducing the issue, tracing the execution path, isolating the root cause, and verifying the fix before moving on.

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 failing test instead of guessing?

To find the root cause of a failing test, you need a structured debugging workflow that enforces explicit reproduction, execution path tracing, and evidence-backed isolation before attempting any fix.

What is the best way to debug silent job failures in production?

The best way to debug silent job failures is through evidence-driven analysis, which requires reproducing the failure and confirming your hypotheses with logs or debugger output to isolate the exact divergence point.

How do I safely fix a regression without introducing new bugs?

To safely fix a regression, apply minimal changes to the code, validate with tests first, and run full regression checks to verify the result end to end before declaring the issue resolved.

Can I use a systematic debugging workflow for broken commands in staging?

Yes, you can use a systematic debugging workflow to diagnose broken commands and unexpected behavior across local, staging, or production environments by tracing execution paths and verifying with logs.

Why should I isolate a bug before applying a fix?

You should isolate a bug before applying a fix because this prevents blind probing, ensuring you understand the exact failure, the expected behavior, and the true root cause before making any changes.