node-inspect-debugger

Debug Node.js applications via the built-in inspector and Chrome DevTools Protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Node.js applications can be painful without an integrated debugging workflow; this Skill provides a reliable way to inspect runtime state using the built-in inspector and the Chrome DevTools Protocol.

Core Features & Use Cases

  • Interactive debugging with node inspect: set breakpoints, step through code, view call stacks, and inspect local and closure scope.
  • CDP scripting with chrome-remote-interface: automate debugging tasks and collect state across runs.
  • Attaching to running processes: pause a node process and inspect its state from a terminal UI.
  • Debug Hermes ui-tui components and other Node-based tooling inside a shell environment.

Quick Start

Launch your target with the inspector enabled and attach your debugger to pause at startup for breakpoints and interactive inspection.

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 Node.js applications in the terminal using the built-in inspector?

Debug Node.js applications in the terminal by launching your target with the inspector enabled and attaching the debugger to set breakpoints, step through code, and inspect call stacks.

Can I automate Node.js debugging tasks with the Chrome DevTools Protocol?

Automate Node.js debugging tasks with the Chrome DevTools Protocol by using the chrome-remote-interface package for scripted workflows that collect runtime state across runs.

Does this Node.js debugging approach work on Linux, macOS, and Windows?

Interactive debugging with node inspect and scripted CDP workflows operate reliably on Linux, macOS, and Windows, requiring only a Node.js runtime to function.

What is the best way to inspect the state of a running Node.js process from a shell?

Inspect a running Node.js process from a shell by pausing it with the built-in inspector to view local and closure scope variables within the terminal UI.

Do I need the chrome-remote-interface package to use node inspect for breakpoints?

Interactive debugging with node inspect requires only a Node.js runtime; the chrome-remote-interface package is an optional dependency needed solely for scripted CDP workflows.

Why use CDP scripting instead of interactive node inspect for debugging?

Use CDP scripting with chrome-remote-interface to automate repeatable debugging tasks and collect state across runs, whereas node inspect provides interactive breakpoint control.