node-inspect-debugger

Debug Node.js applications using the --inspect flag and Chrome DevTools Protocol.

Updated May 25, 2026
One-click install
npx skills add https://github.com/webdevtodayjason/subctl-rust --skill node-inspect-debugger-webdevtodayjason
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/webdevtodayjason/subctl-rust/tree/main/skills/node-inspect-debugger
Command: npx skills add https://github.com/webdevtodayjason/subctl-rust --skill node-inspect-debugger-webdevtodayjason

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit provides a streamlined way to debug Node.js applications using the built-in --inspect flag and the Chrome DevTools Protocol (CDP) via CLI tools, allowing developers to diagnose and fix issues without manual debugging.

Core Features & Use Cases

  • Command Line Inspection: Use node inspect for interactive debugging or ndb for automated debugging tasks.
  • Breakpoints and Stepping: Set breakpoints, step through code, and inspect call stacks and variables.
  • Integration with Hermes TUI: Special guidance for debugging Hermes-based user interfaces and services.
  • Performance Analysis: Capture CPU profiles and heap snapshots for non-interactive debugging.
  • Use Case: When you encounter a bug in a Node.js application that requires detailed inspection of the application state, this Skill unit can be used to quickly diagnose and resolve the issue.

Quick Start

Run the 'node-inspect-debugger' skill to debug your Node.js application at runtime by attaching a debugger to the process with node inspect -p <pid>.

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?▼

Debug Node.js applications by starting the process with the --inspect flag and attaching via the Chrome DevTools Protocol CLI. This allows you to set breakpoints and inspect variables without manual troubleshooting.

Can I capture CPU profiles and heap snapshots for a Node.js process non-interactively?▼

Yes, you can capture CPU profiles and heap snapshots for Node.js non-interactively. This performance analysis helps diagnose complex runtime issues when interactive stepping is not feasible.

Does the node inspect CLI support attaching to an already running process by PID?▼

Yes, the node inspect CLI supports attaching to a running Node.js process using the process ID. Execute `node inspect -p <pid>` to attach the debugger and inspect the live application state.

What is the best way to debug Hermes-based user interfaces in a Node.js environment?▼

The best way to debug Hermes-based user interfaces is using the built-in --inspect flag with Chrome DevTools Protocol. This integration provides special guidance for stepping through Hermes UI services.

Do I need chrome-remote-interface to automate Node.js debugging tasks?▼

Yes, chrome-remote-interface is required as a dependency. It provides the necessary bindings to interact with the Chrome DevTools Protocol for automating interactive and non-interactive Node.js debugging tasks.