debugging

Diagnose software bugs through guided hypothesis testing and step-by-step fix verification.

Updated Apr 8, 2026

Search Tags:#debugging #root-cause #error-analysis #performance-profiling #log-investigation

Ready to run

npx skills add https://github.com/zm2231/personal-os-cowork --skill debugging-zm2231

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/zm2231/personal-os-cowork/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/zm2231/personal-os-cowork --skill debugging-zm2231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers systematically identify, diagnose, and resolve software problems, reducing time spent on error hunting and inefficient trial‑and‑error debugging.

Core Features & Use Cases

Structured problem definition, information gathering, and hypothesis testing.
Step‑by‑step root‑cause isolation, fix implementation, and verification.
Advanced techniques for log analysis, performance profiling, concurrency, and distributed system debugging.
Use cases include fixing runtime errors, performance bottlenecks, memory leaks, race conditions, and infrastructure failures.

Quick Start

Ask the debugging skill to analyze the error message “NullPointerException in UserService” and suggest the next investigation steps.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is the best way to analyze error messages and find a software bug's root cause?▼

Root-cause analysis isolates software bugs by defining the problem, gathering information, and testing hypotheses. This approach delivers step-by-step troubleshooting to systematically pinpoint the exact failure point.

How do I debug performance bottlenecks and memory leaks in my application?▼

Debugging performance bottlenecks and memory leaks requires advanced profiling techniques to analyze resource usage. This method isolates the problematic code paths and verifies the applied fix to restore system performance.

How do I investigate race conditions and concurrency problems during troubleshooting?▼

Investigating race conditions and concurrency problems involves structured hypothesis testing to trace execution threads. This process identifies conflicting resource access patterns and verifies the synchronization fix.

Can I use structured debugging for distributed system failures and log investigations?▼

Structured debugging handles distributed system failures and log investigations by correlating error messages across components. It isolates the failure origin and verifies the resolution without requiring external dependencies.

Do I need external dependencies or specific tools to isolate software errors?▼

No external dependencies are required to isolate software errors. The troubleshooting process relies entirely on guided analysis, hypothesis testing, and fix verification to resolve runtime errors natively.