What problem does it solve?
This Skill solves the problem of not understanding why a Node.js program misbehaves when console logs are insufficient, by letting you pause execution and inspect live state at the exact line you care about.
Core Features & Use Cases
- Breakpoints and stepping: Use Node’s V8 inspector to continue, step into/over/out, pause, and walk the call stack to locate the true failing path.
- Scope inspection and expression evaluation: Inspect locals/closure variables and evaluate arbitrary JavaScript expressions while paused to understand runtime data.
- Automated CDP debugging: Drive Chrome DevTools Protocol from a terminal script to set many breakpoints, capture state across pauses, and reproduce issues non-interactively.
- Use cases: Debug failing Node scripts, trace issues in TypeScript/tsx projects, inspect Ink-based ui-tui behavior, and diagnose runtime problems before they surface in logs.
Quick Start
Use the node-inspect-debugger skill to debug a failing Node script by starting it with --inspect-brk and then using node inspect to set a breakpoint at the suspicious source line and continue execution until it pauses there.