node-inspect-debugger

Inspect Node.js execution state using breakpoints, call stacks, and variable evaluation.

Updated May 9, 2026

Search Tags:#debugging #nodejs #breakpoints #inspector #runtime analysis #chrome devtools protocol

Ready to run

npx skills add https://github.com/pmcdowall/hermes-skills --skill node-inspect-debugger-pmcdowall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/pmcdowall/hermes-skills/tree/main/software-development/node-inspect-debugger
Command: npx skills add https://github.com/pmcdowall/hermes-skills --skill node-inspect-debugger-pmcdowall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers diagnose difficult Node.js runtime issues when basic logging is insufficient by providing interactive inspection, breakpoints, and execution control.

Core Features & Use Cases

Interactive Debugging: Use Node's built-in inspector to step through code, inspect variables, evaluate expressions, and analyze call stacks.
Automated Inspector Workflows: Connect through Chrome DevTools Protocol to script breakpoint management, state collection, CPU profiling, and heap snapshots.
Use Case: Debug complex Node.js applications such as terminal UIs, test runners, asynchronous workflows, or long-running services by tracing execution state directly.

Quick Start

Use the node-inspect-debugger skill to attach a debugger to my Node.js process and help me inspect the failing code path.

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 when logging is not enough?▼

To debug a Node.js application when logging fails, use the built-in inspector to interactively step through code, set breakpoints, inspect variables, and analyze call stacks for runtime failures.

Can I use Chrome DevTools Protocol to script Node.js debugging sessions?▼

Yes, you can use the Chrome DevTools Protocol to script Node.js debugging sessions, enabling automated breakpoint management, state collection, CPU profiling, and heap snapshots for runtime diagnostics.

What is the best way to debug asynchronous Node.js workflows?▼

The best way to debug asynchronous Node.js workflows is by attaching the Node inspector to trace execution state directly, allowing you to evaluate expressions and inspect call stacks during runtime.

Does the Node.js inspector support CPU profiling and heap snapshots?▼

Yes, the Node.js inspector supports CPU profiling and heap snapshots through Chrome DevTools Protocol workflows, allowing you to collect runtime diagnostics and analyze performance issues.

How do I inspect variables and evaluate expressions in a running Node.js process?▼

You can inspect variables and evaluate expressions in a running Node.js process by attaching the Node inspector, which provides interactive execution control and call stack analysis.

What types of Node.js applications can I debug with the inspector?▼

You can debug various Node.js applications with the inspector, including terminal UIs, test runners, asynchronous workflows, and long-running services by tracing execution state directly.