debug

Diagnose and fix software bugs using hypothesis-driven analysis.

2|1|Updated Mar 16, 2026

Search Tags:#automation #agent #debug #hypothesis #bug-fixing #model-routing #developer-tool

Ready to run

npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill debug-byeongminlee

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/debug
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill debug-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to diagnosing and fixing software bugs using hypothesis-driven debugging. It guides you to choose the appropriate debugging model, orchestrate a debugger agent, and record outcomes for traceability.

Core Features & Use Cases

Hypothesis-driven bug analysis with model routing to determine when to use a lightweight haiku model or a fuller sonnet model.
Automated task orchestration that recruits a debugger agent, runs a guided analysis, and validates fixes across features.
Use Case: When a bug spans multiple modules or has unclear reproduction, apply this skill to systematically isolate root causes and verify resolutions.

Quick Start

Run the debug skill on a bug report to start the hypothesis-driven debugging workflow.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I find the root cause of a software bug that spans multiple modules?▼

Hypothesis-driven debugging systematically isolates root causes by orchestrating a debugger agent to analyze complex bugs. It applies model-guided analysis to trace issues across multiple modules and validate reproducible fixes for your software projects.

What is the best way to automate bug-fixing workflows for unclear bug reproductions?▼

Automating bug-fixing for unclear reproductions uses a structured task workflow that recruits a debugger agent. It applies model routing decisions to run guided analysis, systematically isolating root causes and verifying resolutions across cross-feature bugs.

When should I use different AI models for systematic root-cause analysis?▼

During systematic root-cause analysis, model routing determines when to use a lightweight haiku model versus a fuller sonnet model. This optimizes the debugging workflow by matching the model's capability to the complexity of the bug hypothesis being evaluated.

Can I use an automated debugger agent for cross-feature software bugs?▼

Yes, an automated debugger agent handles cross-feature software bugs by running a guided hypothesis-driven analysis. It systematically isolates root causes and validates resolutions across multiple affected modules to ensure reproducible fixes.

Does structured debugging work without adding external dependencies to my project?▼

Structured debugging operates without external dependencies by applying a hypothesis-driven debugger within your existing software projects. It uses model routing and an orchestrated debugger agent to analyze and fix the issue directly.