node-inspect-debugger

Drive Node.js debugging sessions via the built-in inspector and Chrome DevTools Protocol.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill node-inspect-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/ChangZhou-xj/zxj_skill/tree/main/software-development/node-inspect-debugger
Command: npx skills add https://github.com/ChangZhou-xj/zxj_skill --skill node-inspect-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enable efficient debugging of Node.js applications by leveraging the built-in inspector (--inspect or --inspect-brk) and the Chrome DevTools Protocol (CDP) to set breakpoints, inspect scopes, and drive debugging sessions.

Core Features & Use Cases

  • Built-in node inspect CLI for quick, interactive debugging.
  • CDP-based automation using chrome-remote-interface for scripted breakpoints and state capture.
  • Attaching to running processes and debugging Hermes UI components or worker processes.

Quick Start

Launch a Node.js process with --inspect-brk and attach a debugger to pause on the first line.

Frequently Asked Questions about node-inspect-debugger

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

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

Attaching to a running Node.js process for debugging is supported by using the built-in inspector and the Chrome DevTools Protocol (CDP), allowing you to connect a debugger to an active process without restarting it.

What is the best way to automate Node.js debugging sessions with CDP?

Automating Node.js debugging sessions is best achieved by using the Chrome DevTools Protocol (CDP) with a client like chrome-remote-interface, enabling scripted breakpoints and automated runtime state capture for interactive or automated workflows.

Does this approach support debugging worker processes and UI components?

Debugging worker processes and specific UI components like Hermes is supported, allowing you to attach the inspector to various runtime environments and inspect their state using the Chrome DevTools Protocol.

Can I switch between the node inspect CLI and CDP clients during a debugging session?

Switching between the node inspect CLI and CDP clients is supported, allowing you to transition from interactive terminal-based debugging to scripted automation using the Chrome DevTools Protocol within the same workflow.

Why use the built-in node inspect tool versus other debugging approaches?

The built-in node inspect tool provides quick, interactive TUI debugging directly in the terminal without external dependencies, whereas CDP allows for complex, automated state capture and scripted breakpoints.