node-inspect-debugger

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to debugging Node.js applications by leveraging the built-in V8 inspector, allowing developers to move beyond console.log and perform deep state inspection.

Core Features & Use Cases

  • Interactive Debugging: Use the node inspect REPL for real-time breakpoints, call-stack walking, and scope inspection.
  • Programmatic Control: Utilize the Chrome DevTools Protocol (CDP) via chrome-remote-interface to automate debugging tasks, capture heap snapshots, or profile CPU usage.
  • Use Case: When a complex TUI component or background worker behaves unexpectedly, attach the debugger to the running process to inspect local variables and closure states without modifying the source code.

Quick Start

Use the node-inspect-debugger skill to attach to the running process with PID 1234 and set a breakpoint at line 42 of app.js.

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 V8 inspector?

Interactive Node.js debugging uses the built-in V8 inspector through the node inspect REPL to set real-time breakpoints, walk the call stack, and inspect local variables and closure states without modifying the source code.

Can I automate capturing heap snapshots and CPU profiling in Node.js?

You can automate capturing heap snapshots and CPU profiling in Node.js by utilizing the Chrome DevTools Protocol via a CDP client library like chrome-remote-interface, enabling non-interactive programmatic analysis of complex runtime issues.

What is the best way to inspect local variables in a running Node.js background worker?

The best way to inspect local variables in a running Node.js background worker is to attach the V8 inspector debugger to the running process, allowing deep state inspection and closure analysis without adding console log statements.

Do I need a CDP client library to use programmatic debugging for Node.js?

A CDP client library like chrome-remote-interface is required for advanced programmatic debugging and automated non-interactive profiling, but optional for standard interactive CLI-based debugging using the built-in node inspect REPL.

Does Node.js debugging with the V8 inspector support TUI components?

Yes, when a complex TUI component behaves unexpectedly, you can attach the V8 inspector debugger to the running Node.js process to inspect local variables and closure states without modifying the source code.