dev-debug

Debug software defects through a structured subagent iteration loop with test verification.

19|5|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/edwinhu/workflows --skill dev-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-debug
Source: https://github.com/edwinhu/workflows/tree/main/skills/dev-debug
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles complex bugs by employing a rigorous, iterative debugging process, preventing common pitfalls like context pollution and rationalized shortcuts.

Core Features & Use Cases

  • Systematic Debugging Loop: Employs fresh subagents for each iteration to ensure clean context.
  • Progress Gating: Autonomous operation as long as meaningful progress is made, escalating to the user only when stuck.
  • Use Case: When a critical feature is broken and standard debugging methods have failed, this Skill can be invoked to systematically isolate and resolve the root cause without introducing further complexity.

Quick Start

Use the dev-debug skill to investigate and fix the reported bug in the user authentication module.

Frequently Asked Questions about dev-debug

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

FAQPage Schema
How do I systematically debug complex software defects when standard troubleshooting fails?

Systematic debugging requires a multi-phase protocol that isolates root causes through rigorous hypothesis testing. Using fresh subagents for each iteration prevents context drift, ensuring defects are resolved without introducing further complexity or rationalized shortcuts.

What is the best way to prevent context pollution during root cause analysis?

Preventing context pollution during root cause analysis involves employing a structured iteration loop with fresh subagents. This enforces clean context for each testing phase, ensuring hypotheses are rigorously tested before fixes are applied and preventing context drift.

How do I automate bug fixing without missing the root cause?

Automating bug fixing safely requires progress gating and automated test verification. This enforces autonomous operation as long as meaningful progress is made, escalating to the user only when stuck, ensuring fixes target the actual root cause.

Can I use a structured debugging protocol for critical broken features?

A structured debugging protocol is ideal for critical broken features. It systematically isolates and resolves the root cause by enforcing a strict subagent-based iteration loop with automated test verification, preventing context drift.

Why does my debugging process keep introducing new complexity instead of fixing the bug?

Debugging introduces new complexity when context drift and rationalized shortcuts occur. Employing a rigorous, iterative debugging process with progress gating and fresh subagents prevents these pitfalls, ensuring hypotheses are rigorously tested before fixes are applied.

Does automated test verification work with iterative code analysis for troubleshooting?

Automated test verification works with iterative code analysis by enforcing a strict subagent-based iteration loop. This ensures hypotheses are rigorously tested before fixes are applied, preventing context drift during troubleshooting.