dev-debug

Guides a structured debugging workflow to identify root causes, propose fixes, and document resolutions.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Sridhar-Ranganaboina/WebGenie --skill dev-debug-sridhar-ranganaboina
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-debug
Source: https://github.com/Sridhar-Ranganaboina/WebGenie/tree/main/packages/browseros-agent/.claude/skills/dev-debug
Command: npx skills add https://github.com/Sridhar-Ranganaboina/WebGenie --skill dev-debug-sridhar-ranganaboina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a structured debugging workflow to identify root causes, validate fixes, and document changes for code issues.

Core Features & Use Cases

  • Derive a short slug from the issue description and create a dedicated .llm/debug_<slug>/ directory.
  • Generate 2-5 root-cause hypotheses ranked by probability with evidence and relevant files.
  • Provide a step-by-step fix plan, then implement, test, and commit changes.
  • Maintain full traceability by storing notes and results under .llm/debug_<slug>.

Quick Start

Describe the issue clearly to start the debugging workflow.

Frequently Asked Questions about dev-debug

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

FAQPage Schema
How do I perform systematic root-cause debugging for a software issue?

Root-cause analysis for software issues works by generating 2-5 ranked hypotheses based on evidence and relevant files. It then provides a step-by-step fix plan, implements changes, and stores all notes under a dedicated debug directory for traceability.

What is the best way to triage code issues and track the debugging workflow?

Issue management during debugging works by generating a short slug from the issue description to create a dedicated directory. This directory stores all root-cause hypotheses, fix plans, and commit notes, ensuring full traceability across the project.

Can I use this debugging workflow across different software projects?

Yes, this debugging workflow is designed for software issues across multiple projects. It requires only a concise issue description to initiate root-cause analysis, fix implementation, testing guidance, and commit note generation.

Do I need any specific dependencies to start the code analysis and triage process?

No dependencies are required to start the code analysis and triage process. You only need to provide a concise issue description to generate root-cause hypotheses and receive a step-by-step fix plan.

How do I document the resolution and fix plan for a triaged code issue?

Document the resolution by following the provided step-by-step fix plan, implementing changes, and saving commit notes. The workflow automatically stores all testing guidance, results, and interim analyses in a dedicated debug directory.