debugger

Name: debugger
Availability: InStock
Author: goodworkrinkz

Diagnose software issues with a structured six-step debugging workflow.

Updated Mar 23, 2026

Search Tags:#debugging #troubleshooting #logging #problem-solving #reproducibility #root-cause-analysis #stack-trace

Ready to run

npx skills add https://github.com/GOODWORKRINKZ/mylamp --skill debugger-goodworkrinkz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugger
Source: https://github.com/GOODWORKRINKZ/mylamp/tree/main/.agents/skills/debugger
Command: npx skills add https://github.com/GOODWORKRINKZ/mylamp --skill debugger-goodworkrinkz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging and root-cause analysis to identify and fix software issues quickly and reliably.

Core Features & Use Cases

Structured debugging workflow: understand the problem, gather information, form hypotheses, test hypotheses, identify root causes, and verify fixes.
Practical strategies: binary search, rubber duck debugging, and bisecting to isolate faults; strategic logging to capture state and reproduce issues.
Use cases include debugging errors, crashes, performance regressions, intermittent failures, and analysis of stack traces or logs in development, staging, or production environments.

Quick Start

Start by outlining the observed problem, gathering relevant logs or repro steps, then apply the six-step debugging process to locate and verify the root cause.

Frequently Asked Questions about debugger

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

FAQPage Schema

How do I systematically debug software crashes and performance problems?▼

To debug software crashes systematically, apply a structured workflow: understand the problem, gather information, form hypotheses, test them, identify the root cause, and verify the fix.

What's the best way to analyze a stack trace to find the root cause of an error?▼

Analyzing a stack trace requires gathering information from logs, forming hypotheses about the failure point, and testing those hypotheses to isolate the root cause before verifying the applied fix.

How do I reproduce intermittent failures and log the necessary state for troubleshooting?▼

Troubleshooting intermittent failures requires strategic logging to capture state and establishing reproducibility steps, enabling you to form and test hypotheses to pinpoint the fault.

Can I use binary search and bisecting to isolate faults in a large codebase?▼

Yes, you can use binary search and bisecting strategies to systematically isolate faults within a large codebase by narrowing down the revision range or execution path where the issue occurs.

When should I use rubber duck debugging during root-cause analysis?▼

Use rubber duck debugging during root-cause analysis to articulate your problem and thought process, which helps clarify assumptions and form new hypotheses when you are stuck.