Find the nil deref a print loop can't catch
使うタイミング： A specific input causes a panic and you can't see where without a debugger.
前提条件
- Server/skill installed and authenticated — See repo README
フロー
-
Reproduce under debuggerUsing the debug skill, run main_test.go::TestPanicCase under delve with a breakpoint at the panic frame.✓ コピーしました→ Process paused at the panic
-
InspectPrint locals and the call chain. Show me which variable is nil.✓ コピーしました→ Variable value + caller chain
結果： Bug located, not guessed.
注意点
- Breakpoints by symbol can match multiple methods in Go interfaces — Breakpoints by symbol can match multiple methods in Go interfaces — qualify with the package path.