node-inspect-debugger

Debug Node.js applications via Chrome DevTools Protocol with breakpoints and step-through execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface, and includes scripts (resource) components.

What problem does it solve?

This Skill helps developers debug Node.js applications by providing a command-line interface to the Chrome DevTools Protocol, allowing for real-time debugging and inspection.

Core Features & Use Cases

  • Command-Line Debugging: Use node inspect to debug Node.js scripts from the terminal with breakpoints, step-through execution, and more.
  • Automated Breakpoints: Integrate chrome-remote-interface for scriptable debugging, useful for automated testing and long-running processes.
  • Use Case: When you need to investigate a Node.js application that's not behaving as expected, this Skill can attach to the process, set breakpoints, and inspect the state of the application.

Quick Start

Start debugging a script with node inspect path/to/script.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 from the command line?

Use `node inspect path/to/script.js` to debug Node.js applications from the command line. This attaches the Chrome DevTools Protocol to set breakpoints, step through execution, and inspect application state.

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

Yes, you can automate Node.js debugging by integrating the `chrome-remote-interface` dependency, enabling scriptable breakpoints and state inspection for long-running processes and automated testing scenarios.

What do I need to use Chrome DevTools Protocol for Node.js debugging?

To use Chrome DevTools Protocol for Node.js debugging, you need both Node.js and Python installed in your environment to handle breakpoints, step-through execution, and state inspection.

What's the best way to inspect a Node.js process that is behaving unexpectedly?

The best way to inspect an unexpected Node.js process is using `node inspect` to attach to it, set automated breakpoints, and evaluate the real-time application state via the Chrome DevTools Protocol.

Does command-line Node.js debugging support step-through execution?

Yes, command-line Node.js debugging supports step-through execution. By leveraging the Chrome DevTools Protocol, you can pause scripts, step through code line-by-line, and inspect variables.