debugging

Run structured debugging sessions with symptom capture and root cause isolation.

2|Updated Feb 17, 2017

Search Tags:#code analysis #debugging #troubleshooting #issue resolution #structured problem solving

Ready to run

npx skills add https://github.com/John2143/dotfiles --skill debugging-john2143

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/John2143/dotfiles/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/John2143/dotfiles --skill debugging-john2143

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The debugging Skill Unit simplifies the process of troubleshooting software issues by providing a structured methodology for capturing symptoms, formulating hypotheses, isolating causes, and verifying fixes.

Core Features & Use Cases

Structured Debugging Session: Automates the steps of symptom capture, hypothesis testing, and root cause analysis.
Symptom and File Scope: Supports specifying symptoms and file paths for more focused debugging.
Allowed Tools: Interacts with read, bash, debug, search, and LSP for enhanced analysis capabilities.
Usage: Trigger the debugging process with a command, providing symptoms and file paths as necessary.

Quick Start

/skill:debugging "application hangs at startup"

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I structure a debugging session for software troubleshooting?▼

Structured debugging works by guiding you through symptom capture, hypothesis formulation, root cause isolation, and fix verification. It provides a systematic methodology for software troubleshooting across multiple programming environments and codebases.

How do I troubleshoot application issues using a structured problem solving approach?▼

Troubleshoot application issues by initiating a debugging workflow with a command, specifying the observed symptoms and relevant file paths. This scopes the analysis to isolate the root cause and verify the resolution interactively or via command-line.

Can I use code analysis tools to isolate root causes in specific file paths?▼

Yes, code analysis isolates root causes by scoping the debugging session to specified file paths. The workflow leverages read, search, LSP, bash, and debug tools to analyze the targeted codebase and verify the identified cause.

Does this structured problem solving approach work across multiple programming environments?▼

Yes, this structured problem solving approach is intended for software troubleshooting across multiple programming environments and codebases. It supports interactive and command-line interactions to initiate the debugging workflows regardless of the specific environment.

What are the limitations of structured debugging for issue resolution?▼

The main limitation of structured debugging is that it requires accurate symptom descriptions and file path scopes to be effective. While it supports interactive and command-line workflows, the quality of root cause isolation depends entirely on the initial hypothesis formulation.