dbg

Diagnose runtime bugs and performance bottlenecks across debugger backends.

15|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/redknightlois/dbg --skill dbg-redknightlois
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbg
Source: https://github.com/redknightlois/dbg/tree/main/skills
Command: npx skills add https://github.com/redknightlois/dbg --skill dbg-redknightlois

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dbg removes the guesswork from runtime diagnosis by letting you inspect live variables, call stacks, breakpoints, and performance signals instead of repeatedly editing code and hoping the bug disappears.

Core Features & Use Cases

  • Persistent debugging sessions: Start a target once, step through execution, inspect locals, and keep captures for later replay.
  • Cross-language backend support: Work through one interface across Rust, C, C++, Python, Go, .NET, Java, JavaScript, Ruby, PHP, Haskell, OCaml, and more.
  • Performance and disassembly workflows: Profile hotspots, inspect hot paths, compare runs, and view JIT or native assembly when optimization questions matter.
  • Real-world use case: Use dbg to stop a crashing service at the failing line, inspect the actual runtime value, and confirm the root cause before changing code.

Quick Start

Ask the agent to run dbg against your target, set the most relevant breakpoint, continue until the stop, and explain the observed runtime state.

Frequently Asked Questions about dbg

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

FAQPage Schema
How do I debug runtime bugs and inspect live variables without editing code?

Debug runtime bugs by attaching to a live process to inspect variables, call stacks, and breakpoints. dbg lets you stop a crashing service at the failing line and confirm the root cause before changing code.

Can I use one debugger interface for Go, Python, C++, and JavaScript backends?

Yes, you can use one debugger interface across Rust, Go, Python, C++, JavaScript, and more. dbg works through backend adapters like Delve, LLDB, and V8 inspector to launch targets and inspect live state.

How do I profile performance bottlenecks and inspect disassembly during a debugging session?

Profile performance bottlenecks and inspect disassembly by capturing hot paths and comparing runs. dbg supports profiling hotspots and viewing JIT or native assembly to resolve optimization questions.

Do I need external debugger tools like LLDB or Valgrind to run dbg?

Yes, you need external debugger tools and backend adapters to run dbg. It requires backends such as LLDB, Delve, netcoredbg, jdb, phpdbg, Valgrind, dotnet-trace, or V8 inspector to launch targets and inspect live state.

What is persistent debugging and can I replay captured runtime states later?

Persistent debugging keeps your session active so you can step through execution and save captures for later replay. dbg allows you to start a target once, inspect locals, and retain hit captures for future analysis.

What is the best way to diagnose a crashing service and find the root cause?

The best way to diagnose a crashing service is using live debugging to stop at the failing line and inspect the actual runtime value. dbg removes the guesswork by letting you observe live state directly before modifying code.