deep-debug

Name: deep-debug
Availability: InStock
Author: fefogarcia

Coordinate parallel agents to trace execution and map entry points for debugging.

1|Updated Feb 10, 2026

Search Tags:#code analysis #debugging #troubleshooting #bug fixing #multi-agent #browser tools

Ready to run

npx skills add https://github.com/fefogarcia/approved-skills --skill deep-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deep-debug
Source: https://github.com/fefogarcia/approved-skills/tree/main/skills/deep-debug
Command: npx skills add https://github.com/fefogarcia/approved-skills --skill deep-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill tackles stubborn bugs that resist conventional debugging, especially those involving complex interactions, browser behavior, or unclear symptoms.

Core Features & Use Cases

Multi-Agent Investigation: Launches parallel AI agents with distinct roles (tracer, reviewer, explorer) to analyze bugs from multiple angles.
Evidence-Driven Debugging: Leverages browser tools (network requests, console logs) and code analysis to gather concrete evidence before forming hypotheses.
Use Case: You're facing a bug where API calls are duplicating intermittently. This Skill will use browser network logs and code analysis agents to pinpoint the exact React hook or event handler causing the issue.

Quick Start

Use the deep-debug skill to investigate the bug described as 'API calls are duplicating'.

Frequently Asked Questions about deep-debug

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

FAQPage Schema

How do I debug complex software bugs involving frontend and backend interactions?▼

Multi-agent debugging helps resolve complex software bugs by launching parallel AI agents to systematically gather evidence from browser tools and code, tracing execution and analyzing patterns to pinpoint root causes.

What is the best way to find the root cause of intermittent API call duplications?▼

The best way to find the root cause of intermittent API call duplications is evidence-driven debugging, which leverages browser network logs and parallel code analysis agents to pinpoint the exact event handler causing the issue.

Can I use browser tools for code analysis when troubleshooting stubborn bugs?▼

Yes, you can use browser tools for code analysis when troubleshooting stubborn bugs. The process integrates browser network requests and console logs with parallel agents to gather concrete evidence before forming hypotheses.

How does multi-agent debugging work for tracing execution and mapping entry points?▼

Multi-agent debugging works by deploying parallel agents with distinct roles, such as tracers and explorers, to analyze execution paths and map entry points simultaneously, systematically isolating the underlying defect.

Do I need specific dependencies to perform evidence-driven debugging?▼

You need browser interaction tools and code analysis capabilities to perform evidence-driven debugging. These dependencies allow the agents to gather concrete network and console evidence for diagnosing frontend and backend issues.

When should I use multi-agent debugging instead of conventional troubleshooting?▼

You should use multi-agent debugging instead of conventional troubleshooting when facing stubborn bugs that resist standard methods, especially those involving complex interactions, unclear symptoms, or unpredictable browser behavior.