node-inspect-debugger

Debug Node.js applications via Chrome DevTools Protocol CLI.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/srivtx/supercharger-opencode --skill node-inspect-debugger-srivtx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/srivtx/supercharger-opencode/tree/main/engineering/node-inspect-debugger
Command: npx skills add https://github.com/srivtx/supercharger-opencode --skill node-inspect-debugger-srivtx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides tools to debug Node.js applications using the Chrome DevTools Protocol CLI, allowing for in-depth inspection and debugging of Node.js applications.

Core Features & Use Cases

  • Debugging via CLI: Use node inspect and ndb to debug Node.js applications programmatically from the terminal.
  • Breakpoints and Stepping: Set breakpoints, step in/over/out, and inspect call stacks and variable scopes.
  • Use Case: When a Node.js application fails and you need to understand the intermediate state, or when you want to automate debugging processes.

Quick Start

Use the node-inspect-debugger skill to debug a Node.js application by running the following command: 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?

To debug Node.js applications from the command line, use the `node inspect` command followed by your script path to launch an interactive debugging session via the Chrome DevTools Protocol.

What's the best way to set breakpoints and inspect variables in Node.js without a GUI?

Use the Chrome DevTools Protocol CLI to debug Node.js applications without a GUI, supporting breakpoints, stepping in/over/out, and inspecting call stacks and variable scopes programmatically.

Can I use Chrome DevTools Protocol to automate debugging for Node.js scripts?

Yes, you can automate debugging for Node.js scripts using the Chrome DevTools Protocol CLI, which is suitable for automated debugging processes to inspect application state.

Does the node inspect debugger require any specific dependencies or environments?

Yes, using the node inspect debugger requires Node.js and Chrome DevTools Protocol support to debug applications, with no additional dependencies required.

Why use a CLI debugger for Node.js instead of an IDE?

Use a CLI debugger for Node.js to understand application failures or automate debugging processes from the terminal without needing a full IDE environment.

What limitations should I expect when debugging Node.js via the Chrome DevTools Protocol CLI?

When debugging Node.js via the Chrome DevTools Protocol CLI, expect limitations including terminal-only interaction without visual IDE interfaces, and a strict requirement for Node.js and CDP support.