debugging

Diagnoses and fixes software bugs via a structured reproduction-to-verification workflow.

14|4|Updated Jan 14, 2026

Search Tags:#debugging #troubleshooting #software-engineering #root-cause-analysis #bug-fix #debugging-workflow

Ready to run

npx skills add https://github.com/aiyuekuang/LLMProxy --skill debugging-aiyuekuang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/aiyuekuang/LLMProxy/tree/main/.windsurf/skills/debugging
Command: npx skills add https://github.com/aiyuekuang/LLMProxy --skill debugging-aiyuekuang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to systematically diagnose and fix software bugs, reducing time to resolution.

Core Features & Use Cases

Step-by-step debugging workflow covering reproduction, isolation, hypothesis formation, testing, and verification.
Practical patterns for common bug situations (nil references, race conditions, timeouts, and performance issues).
Guidance for both frontend and backend debugging, including logging, tool usage, and safe debugging practices in production-like environments.

Quick Start

Observe a bug in your app and apply the step-by-step debugging process to reproduce, identify root cause, implement a fix, and verify its effectiveness.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is a systematic debugging workflow for software engineering?▼

A systematic debugging workflow provides a structured approach to diagnose and fix bugs through reproduction, isolation, hypothesis testing, and verification. It ensures a repeatable process for resolving software issues across frontend and backend codebases.

How do I troubleshoot production incidents and bug reports step by step?▼

Troubleshoot production incidents by applying a step-by-step debugging workflow: reproduce the issue, isolate the failing component, form a hypothesis, test the fix, and verify the resolution. This structured process ensures safe debugging in production-like environments.

Does this debugging process work for both frontend and backend codebases?▼

Yes, this debugging process works for both frontend and backend codebases. It provides practical patterns and guidance for logging, tool usage, and safe debugging practices applicable across diverse software engineering environments.

What is the best way to fix race conditions and timeout performance issues?▼

The best way to fix race conditions and timeout performance issues is to follow a structured root cause analysis workflow. It guides you through isolating the concurrency or timing bug, testing your hypothesis, and verifying the fix.

How do I identify the root cause of a nil reference bug during development?▼

Identify the root cause of a nil reference bug by systematically isolating the failure point and testing your hypothesis. The debugging workflow provides practical patterns for resolving common nil references during development sessions.

When should I use a structured root cause analysis instead of ad hoc debugging?▼

Use a structured root cause analysis instead of ad hoc debugging when you need a repeatable approach to systematically diagnose bugs. It is particularly effective for complex bug reports, production incidents, and persistent issues across software teams.