node-inspect-debugger

Drive Node.js debugging via CDP to set breakpoints and inspect runtime state.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill node-inspect-debugger-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill node-inspect-debugger-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Node.js applications often requires manual console logging or brittle setups. This Skill provides a structured approach to using the built-in inspector and Chrome DevTools Protocol to set breakpoints, inspect runtime state, and drive debugging workflows from an agent or terminal.

Core Features & Use Cases

  • Attach to running Node processes with --inspect and use node inspect for interactive debugging.
  • Drive Chrome DevTools Protocol programmatically via chrome-remote-interface for automated state capture and scripted debugging.
  • Debug Hermes ui-tui and other Node-based components by inspecting call frames, scopes, and variables across asynchronous boundaries.

Quick Start

Start the target with node --inspect-brk your-script.js and attach the debugger to begin stepping.

Frequently Asked Questions about node-inspect-debugger

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

FAQPage Schema
How do I debug a Node.js application using the built-in inspector?

Debug Node.js applications using the built-in inspector by starting your script with node --inspect-brk and attaching the node inspect debugger to set breakpoints, inspect runtime state, and control execution.

Can I programmatically control Chrome DevTools Protocol for Node.js debugging?

Yes, you can programmatically drive Chrome DevTools Protocol (CDP) via chrome-remote-interface to automate state capture and perform scripted Node.js debugging across asynchronous boundaries.

What is the best way to attach a debugger to an already running Node process?

Attach a debugger to a running Node process by starting it with the --inspect flag, then use node inspect or chrome-remote-interface to interactively connect and inspect call frames, scopes, and variables.

Does this Node.js debugging approach work with UI components like Hermes ui-tui?

Yes, this approach supports debugging Node-based components like Hermes ui-tui by inspecting call frames, scopes, and variables across asynchronous boundaries within the runtime environment.

Do I need external dependencies to set breakpoints and inspect runtime state in Node.js?

No external dependencies are required to set breakpoints and inspect runtime state; the Skill leverages the built-in Node.js inspector and Chrome DevTools Protocol directly for reliable debugging workflows.