jds-debug

Enforce a four-phase debugging workflow before applying any fix.

13|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/josipmusa/jds --skill jds-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jds-debug
Source: https://github.com/josipmusa/jds/tree/main/skills/jds-debug
Command: npx skills add https://github.com/josipmusa/jds --skill jds-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JDS-debug enforces a structured, four-phase debugging workflow (Investigate → Analyze → Hypothesize → Fix) to prevent symptom-patching and ensure root-cause analysis before any fix.

Core Features & Use Cases

  • Phase-driven debugging process that guides evidence collection, pattern spotting, and hypothesis testing.
  • Iteration tracking with clear progression through Investigate, Analyze, Hypothesize, and Fix, including escalation when multiple fixes fail.
  • Guardrails that require failing tests, verification, and regression checks to ensure durable fixes.

Quick Start

Reproduce the issue and follow the four-phase workflow in order to identify the root cause before attempting a fix.

Frequently Asked Questions about jds-debug

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

FAQPage Schema
What is a systematic root-cause debugging workflow?

Root-cause debugging prevents symptom-patching by enforcing a four-phase workflow: Investigate, Analyze, Hypothesize, and Fix. It requires evidence collection and hypothesis testing before applying any code changes to ensure durable remediation.

How do I trace a bug using a structured debugging process?

Tracing bugs using a structured debugging process involves reproducing the issue, collecting evidence in the Investigate phase, spotting patterns during Analyze, forming a Hypothesis, and applying a safe Fix only after validating the root cause.

What's the best way to stop symptom-patching when fixing code failures?

To stop symptom-patching, enforce a four-phase debugging workflow requiring hypothesis testing before fixes. This approach ensures you verify the root cause of unexpected behavior rather than applying immediate, untested code changes.

What should I do if multiple bug fixes fail to resolve unexpected behavior?

When multiple bug fixes fail to resolve unexpected behavior, a structured debugging workflow triggers an escalation. This iteration tracking mechanism prevents repeated unsuccessful fixes by forcing a re-evaluation of collected evidence and root-cause hypotheses.

Does root-cause debugging require failing tests before applying a fix?

Yes, root-cause debugging requires failing tests before applying a fix. The workflow enforces guardrails that mandate failing-test validation and regression checks to ensure the remediation is safe and resolves the original failure.