debugging

Diagnose and fix codebase bugs through a four-phase evidence-based investigation.

5|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill debugging-jstoup111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/debugging
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill debugging-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures a systematic approach to debugging, reducing the time spent on ineffective fixes and promoting code quality by requiring evidence-based diagnosis.

Core Features & Use Cases

  • Systematic Investigation: Guides through a four-phase process to investigate and identify the root cause of bugs.
  • Evidence-Based Diagnosis: Requires stating a hypothesis with a grounded confidence percentage and its basis.
  • Design Conformance: Ensures that any fix adheres to the approved design, preventing work on code that is scheduled for deletion.
  • Memory Checkpoint: Persists valuable root causes in memory for future reference.
  • Use Case: Ideal for developers who want to streamline their debugging process and ensure they are addressing the true root causes of issues.

Quick Start

Run the 'debugging' skill when encountering a bug or unexpected behavior. Follow the guided investigation process, from investigation and pattern analysis to hypothesis and fix implementation.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I find the root cause of a bug using a systematic investigation process?

Root cause analysis uses a systematic debugging framework to guide developers through a four-phase investigation, ensuring evidence-based diagnosis and pattern analysis before implementing a fix.

What is evidence-based diagnosis and how does it prevent ineffective bug fixing?

Evidence-based diagnosis requires stating a hypothesis with a grounded confidence percentage and its factual basis, preventing ineffective bug fixing by ensuring fixes target the true root cause.

How do I ensure my bug fix adheres to the approved software design?

Design conformance ensures your bug fix adheres to the approved design, preventing wasted effort on modifying code that is scheduled for deletion or does not meet quality standards.

Do I need Python libraries to run a systematic debugging investigation?

Yes, systematic debugging requires Python libraries to execute scripts used for gathering evidence and analyzing data during the investigation phases to diagnose codebase bugs.

How should I persist valuable root causes for future debugging reference?

You can persist valuable root causes using the memory checkpoint feature, which stores identified root causes in memory to streamline future systematic debugging and bug fixing efforts.

What is the best way to structure a codebase investigation for unexpected behavior?

The best way to structure a codebase investigation is following a guided process from initial investigation and pattern analysis to hypothesis formation and final fix implementation.