node-inspect-debugger

Debug Node.js processes via the Chrome DevTools Protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When console.log statements are insufficient for diagnosing Node.js behavior, this skill enables using the built-in Node.js inspector and CDP to inspect runtime state, set breakpoints, and interact with the running process from the command line.

Core Features & Use Cases

  • Attach to running Node.js processes to inspect call stacks, scope variables, and runtime state with node inspect or CDP tooling.
  • Start new processes with --inspect or --inspect-brk to pause at startup and drive debugging sessions programmatically.
  • Automate and script debugging workflows using CDP-compatible tools to collect traces, evaluate expressions, and manage breakpoints.

Quick Start

Attach a debugger to a running Node.js process or launch a script with --inspect-brk to begin interactive debugging.

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 running Node.js process from the command line?

Debug a running Node.js process by attaching the built-in inspector via node inspect or Chrome DevTools Protocol to inspect call stacks, scope variables, and runtime state directly from the command line.

What is the difference between --inspect and --inspect-brk when starting a Node.js script?

The --inspect flag starts a Node.js process with the inspector enabled, while --inspect-brk pauses execution at startup to allow immediate programmatic debugging and breakpoint configuration before code runs.

Can I automate Node.js breakpoints and runtime state inspection programmatically?

Automate Node.js debugging workflows by driving CDP-compatible tools like chrome-remote-interface to script breakpoints, evaluate expressions, collect traces, and manage runtime state inspection.

When should I use the Node.js inspector instead of console.log for debugging?

Use the Node.js inspector when console.log statements are insufficient for diagnosing behavior, enabling interactive REPL exploration, call stack inspection, and runtime state evaluation of running processes.

Does the Node.js inspector support connecting with Chrome DevTools Protocol tooling?

The Node.js inspector supports Chrome DevTools Protocol connections, allowing developers to use node inspect and CDP-compatible tools to attach to processes and automate debugging tasks.

What are the limitations of using node inspect for local development debugging?

Node inspect is designed for local development workflows where developers attach to running processes or start scripts with --inspect, focusing on command-line interaction rather than remote or production environment debugging.