skills.rest
jleechanorg
jleechanorgOFFICIAL
Explore all skills by this author →
GitHub

node-inspect-debugger

Drive Node.js debugging sessions using the V8 inspector and Chrome DevTools Protocol.

Updated Jun 28, 2026
Search Tags:#debugging#cdp#nodejs#breakpoints#tui#inspector
One-click install
npx skills add https://github.com/jleechanorg/hermes-agent --skill node-inspect-debugger-jleechanorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/jleechanorg/hermes-agent/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/jleechanorg/hermes-agent --skill node-inspect-debugger-jleechanorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Node.js debugging can be tedious without a programmable workflow. This Skill enables controlling the built-in V8 inspector and Chrome DevTools Protocol from the terminal or automation scripts, providing breakpoints, call stacks, and local scope dumps to diagnose issues quickly.

Core Features & Use Cases

  • Interactive debugging with node inspect for quick, local investigations.
  • CDP scripting via ndb / chrome-remote-interface for automating breakpoints and state collection.
  • Attaching to running processes (via startup flags or SIGUSR1) for post-mortem and long-running tasks.

Quick Start

Start your target with node --inspect-brk path/to/script.js and attach a debugger to set breakpoints and inspect variables.

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 by starting your script with the --inspect or --inspect-brk flag, then attaching a debugger like node inspect to set breakpoints and inspect variables. This enables interactive terminal-based debugging sessions.

Can I attach a debugger to an already running Node.js process?▼

Yes, you can attach a debugger to running Node.js processes by either starting the process with inspector flags or sending the SIGUSR1 signal, allowing post-mortem debugging and inspection of long-running workers.

What is the Chrome DevTools Protocol and how does it apply to Node.js debugging?▼

The Chrome DevTools Protocol (CDP) drives V8 inspector sessions for Node.js, enabling programmatic control over breakpoints, stepping, and local scope dumps via clients like chrome-remote-interface for automated state collection.

Does this debugging approach work for UI-driven Node.js apps and long-running workers?▼

Yes, this breakpoint-driven workflow applies to local development, long-running workers, and UI-driven Node.js apps, supporting thorough state inspection across different session types using the built-in inspector.

What's the best way to automate breakpoint setting and state collection in Node.js?▼

Use CDP scripting via chrome-remote-interface to automate breakpoints and state collection. This approach allows programmatic control over the V8 inspector to diagnose issues quickly without manual intervention.

Related Skills

Explore More Software Engineering Skills→
markwang2658markwang2658
31

node-inspect-debugger

Debug Node.js processes via the Chrome DevTools Protocol.

Community
Intermediate
vanducngvanducng
5

browser-trace

Capture read-only DevTools Protocol traces from browser automation sessions into NDJSON.

Community
Advanced
SatangThevalueSatangThevalue

node-inspect-debugger

Debug Node.js applications via inspector and Chrome DevTools Protocol.

Community
Advanced
redknightloisredknightlois
15

dbg

Diagnose runtime bugs and performance bottlenecks across debugger backends.

Community
Advanced