node-inspect-debugger

Debug Node.js applications programmatically via the built-in inspector and CDP.

11|Updated May 17, 2026
One-click install
npx skills add https://github.com/StarryCod/cogitum --skill node-inspect-debugger-starrycod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/StarryCod/cogitum/tree/main/cogitum/data/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/StarryCod/cogitum --skill node-inspect-debugger-starrycod

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Node.js debugging often requires external tools and manual inspection; this Skill enables programmatic debugging using the built-in inspector and Chrome DevTools Protocol from the terminal.

Core Features & Use Cases

  • Breakpoints, stepping, and call-stack inspection via node inspect or CDP clients.
  • Attach to running Node processes (including in containers) and inspect locals, closures, and runtime state.
  • Automate repetitive debugging tasks with scripted CDP flows and reproducible sessions.

Quick Start

Start a paused Node.js session with the inspector and attach a CDP client to begin setting breakpoints and inspecting runtime state.

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

Yes, you can attach a CDP client to running Node.js processes inside containers to inspect locals, closures, and runtime state. This remote debugging capability allows you to query and control execution without modifying the deployed application code.

Can I automate repetitive Node.js debugging tasks with scripted CDP flows?

The primary prerequisites for Node.js CDP debugging are a running Node.js process launched with --inspect or --inspect-brk, and a CDP client like chrome-remote-interface to establish the connection for querying and controlling execution.

Does the node inspect client offer the same capabilities as a programmatic CDP client?

The built-in node inspect client provides interactive terminal debugging with breakpoints and call-stack inspection, while a programmatic CDP client enables scripted, automated flows for reproducible sessions and deeper runtime state querying in CI pipelines.

What Node.js runtime states can I inspect when attaching via the Chrome DevTools Protocol?

When attaching via the Chrome DevTools Protocol, you can inspect Node.js runtime states including locals, closures, and the call stack. CDP allows you to evaluate expressions and query execution state programmatically during local or remote debugging.