What problem does it solve?
This Skill solves the problem of debugging complex Node.js runtime issues where simple console.log statements cannot access closure variables, async hang points, or pre-render UI state, eliminating guesswork when troubleshooting failing tests, misbehaving terminal interfaces, or long-running background processes.
Core Features & Use Cases
- Built-in REPL Debugging: Use Node's zero-install node inspect CLI to set breakpoints, step through code, inspect local and closure scope, and evaluate expressions in paused frames for quick troubleshooting.
- Scriptable CDP Automation: Leverage the Chrome DevTools Protocol via chrome-remote-interface to automate breakpoint setup, collect runtime state across runs, and debug non-interactively from agent loops.
- Specialized Workflows: Includes pre-defined steps for debugging Hermes ui-tui Ink components, Vitest test runs, and capturing CPU profiles or heap snapshots for performance analysis. Common use cases include troubleshooting failing Node tests, inspecting pre-render React/Ink state, debugging TUI gateway child processes, and diagnosing async code hangs.
Quick Start
Use the node-inspect-debugger skill to attach a debugger to your target Node.js process, set breakpoints at specific code locations, and inspect local variable values when execution pauses to identify the root cause of runtime issues.