node-inspect-debugger

Drive breakpoints and runtime inspection in Node.js via the Chrome DevTools Protocol.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug Node.js applications by leveraging the built-in inspector and the Chrome DevTools Protocol to drive breakpoints, inspect scope, and evaluate expressions from the terminal or scripted flows.

Core Features & Use Cases

  • Breakpoint-driven debugging: set breakpoints, step through code, inspect call stacks, and dump local/closure state.
  • CDP scripting: automate debugging tasks from Node or Python clients using the Chrome Debugging Protocol.
  • Attaching to running processes: attach to long‑running servers or TUI components and diagnose issues without restarting.
  • IDE-less workflows for agents: integrate with UI-tui or agent loops to introspect runtime state during operation.

Quick Start

Attach the debugger to a running Node.js process by enabling --inspect or --inspect-brk and connecting with node inspect or a CDP client.

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 terminal without an IDE?

Debug Node.js applications from the terminal by starting the process with --inspect or --inspect-brk and connecting via the node inspect command to set breakpoints and evaluate expressions.

Can I attach a debugger to a running Node.js server without restarting it?

Yes, you can attach a debugger to long-running Node.js servers by enabling the inspect protocol, allowing you to diagnose issues and inspect runtime state without restarting the process.

How does the Chrome DevTools Protocol work for scripting Node.js debugging sessions?

The Chrome DevTools Protocol (CDP) scripts Node.js debugging sessions by using a client like chrome-remote-interface to automate breakpoint management, runtime inspection, and expression evaluation across processes.

Do I need a specific Node.js version to use the inspect debugger?

You need a Node.js version that supports the built-in inspector and the --inspect or --inspect-brk flags to enable CDP connections for driving breakpoints and stepping through code.

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

Automate Node.js debugging in agent workflows by using a CDP client to programmatically drive breakpoints, introspect runtime state, and evaluate expressions across Node processes without an IDE.

Why use CDP over the built-in node inspect command for Node.js debugging?

Using a CDP client over the built-in node inspect command enables scripted and automated debugging flows, allowing agents to programmatically control runtime inspection and step through code.