node-inspect-debugger

Automate Node.js debugging via the inspector and Chrome DevTools Protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Node.js debugging often requires manual setup; this skill provides programmatic control of the built-in inspector and Chrome DevTools Protocol to streamline breakpoints, evaluation, and state inspection.

Core Features & Use Cases

  • Attach to a running Node.js process or start with --inspect-brk to pause on entry.
  • Set breakpoints, inspect local and closure scope, walk the call stack, and evaluate expressions.
  • Automate debugging workflows in agent loops or scripted runs for reproducible debugging sessions.

Quick Start

Attach the inspector to a Node.js process and begin interactive debugging.

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 Chrome DevTools Protocol?

You can debug a Node.js application by interfacing directly with the built-in inspector and Chrome DevTools Protocol to set breakpoints, inspect state, and step through code execution programmatically.

Can I attach an inspector to a running Node.js process to inspect local variables?

Yes, you can attach the inspector to a running Node.js process or start with --inspect-brk to pause on entry, allowing you to inspect local and closure scope and evaluate expressions.

What is the best way to automate Node.js debugging workflows in scripted runs?

Automating Node.js debugging workflows is achieved by programmatically controlling the Chrome DevTools Protocol within agent loops or scripted runs to ensure reproducible debugging sessions.

Does this approach support stepping through code and walking the call stack in Node.js?

Yes, this approach supports stepping through code execution, walking the call stack, inspecting local and closure scope, and evaluating expressions during your Node.js debugging session.

Can I use this method for both interactive and automated agent debugging contexts?

Yes, this method applies to development tasks requiring remote control of Node.js processes in both interactive TUI contexts and automated agent contexts for reproducible workflows.