Go Debug

This skill drives an interactive dlv debugging session through tmux from a single context, without delegating to a subagent. The agent calls one helper script (scripts/dlv-session.sh) per dlv command and gets back just the new output, so each step is small enough to reason about.

When to Use

Reach for this skill when source reading alone is not enough:

• A bug only reproduces at runtime and the failure mode (panic, wrong value, hang) needs to be observed in flight.
• A test fails and the why is hidden — stepping into the failing line reveals state that logging would not.
• An integration test hangs, deadlocks, or behaves differently from the unit tests — attach to the process and inspect goroutines.
• A long-running server (lnd, eclair, a daemon under test) is misbehaving in a way that only shows up after warm-up. Use attach rather than restarting under the debugger.
• A concurrent bug needs goroutine-by-goroutine inspection (goroutines, goroutine N, stack).
• Stepping is wanted to confirm the exact control flow through a complex branch, not just "I think it takes this path."

Skip the skill when the bug is obvious from a grep or a unit test would be faster to write.

Prerequisites