node-inspect-debugger

Control the Node.js V8 inspector for breakpoints, call stacks, and heap snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface.

What problem does it solve?

This skill resolves complex runtime issues in Node.js applications by providing deep visibility into execution state, call stacks, and variable scopes that standard logging cannot reach.

Core Features & Use Cases

  • Interactive Debugging: Perform step-by-step execution, breakpoint management, and scope inspection directly from the terminal.
  • Automated Analysis: Use the Chrome DevTools Protocol (CDP) to script non-interactive debugging sessions, capture heap snapshots, or generate CPU profiles.
  • Use Case: When a TUI component or background worker behaves unexpectedly, use this skill to attach to the running process, set conditional breakpoints, and inspect closure variables in real-time.

Quick Start

Use the node-inspect-debugger skill to attach to a running Node.js process by its PID and set a breakpoint at a specific line in your source file.

Frequently Asked Questions about node-inspect-debugger

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

FAQPage Schema
How do I programmatically debug a Node.js application using the V8 inspector?

You can programmatically debug Node.js applications by attaching to the V8 inspector using the Chrome DevTools Protocol to manage breakpoints, analyze call stacks, and inspect variable scopes.

How do I capture heap snapshots and CPU profiles for a Node.js process non-interactively?

You can capture heap snapshots and generate CPU profiles non-interactively by scripting automated debugging sessions that communicate with the Node.js runtime via the Chrome DevTools Protocol.

Can I set conditional breakpoints and inspect closure variables in a running Node.js process?

Yes, you can attach to a running Node.js process to set conditional breakpoints and inspect closure variables in real-time, providing deep visibility into execution state beyond standard logging.

Do I need the chrome-remote-interface library to automate CDP-based debugging sessions?

Yes, the chrome-remote-interface library is required as a dependency to facilitate advanced CDP-based automation and establish programmatic control over the Node.js V8 inspector.

What is the best way to debug unexpected behavior in Node.js background workers without relying on logs?

Attaching directly to the running process via the V8 inspector allows you to perform step-by-step execution, manage breakpoints, and inspect runtime scopes to resolve complex worker issues.

When should I use V8 inspector automation instead of standard Node.js logging?

V8 inspector automation is necessary when standard logging cannot reach the root cause, requiring deep visibility into execution state, call stacks, and variable scopes to resolve complex runtime issues.