debugging

Diagnose runtime bugs by forming and confirming root-cause hypotheses.

5|Updated May 17, 2026
One-click install
npx skills add https://github.com/islee23520/lfg --skill debugging-islee23520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/islee23520/lfg/tree/main/skills/debugging
Command: npx skills add https://github.com/islee23520/lfg --skill debugging-islee23520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you investigate real runtime failures by grounding every conclusion in observed state, not guesses from code reading. It is designed to prevent wasted time on crashes, hangs, silent failures, timing bugs, and confusing behavior across languages and binaries.

Core Features & Use Cases

  • Hypothesis-driven investigation: Form multiple competing explanations, gather distinguishing evidence, and narrow to the true cause.
  • Runtime-specific debugging: Use the right workflow for Python, Node, Rust, Go, native binaries, or bundled apps instead of forcing one generic approach.
  • Specialist tooling: Apply Playwright for browser issues, pwndbg for native binaries, and language-specific debuggers when the situation calls for them.
  • Safe fix validation: Confirm the cause by toggling it, lock it with a failing-first test, verify the real scenario, and clean up every debug artifact.

Quick Start

Use the debugging skill to inspect the failing system, read the matching runtime references, and begin a hypothesis-driven investigation with journaled evidence.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I find the root cause of a runtime crash instead of guessing from code reading?

To find a runtime crash root cause, form multiple competing hypotheses, gather distinguishing observed state evidence, and narrow to the true cause. Apply a red-green workflow with journaled evidence to confirm the diagnosis.

What's the best way to debug silent failures or async misbehavior across different runtimes?

Debugging silent failures or async misbehavior requires runtime-specific references and specialist debuggers. Use the correct workflow for Python, Node, Rust, Go, or native binaries instead of forcing a generic approach.

Can I use Playwright or pwndbg for investigating browser-driven apps and native binary crashes?

Playwright works for browser-driven app issues, while pwndbg applies to native binaries. Specialist tooling matches the runtime environment to accurately collect observed state and confirm the root cause.

How do I validate a runtime bug fix and ensure my debug artifacts are cleaned up?

Validate a runtime bug fix by toggling the cause, locking it with a failing-first test, and verifying the real scenario. Complete the red-green workflow by cleaning up every debug artifact left during investigation.

Does hypothesis-driven debugging work for reverse-engineering tasks and timing bugs?

Hypothesis-driven debugging works for reverse-engineering tasks and timing bugs by forming competing explanations and gathering distinguishing evidence to confirm the root cause from observed state.

When should I not rely on static code analysis for diagnosing runtime bugs?

Avoid static code analysis for runtime bugs involving crashes, hangs, silent failures, or async misbehavior. These require hypothesis-driven investigation grounded in observed state collected from the actual runtime environment.