skills.rest
Gitnapp
GitnappCOMMUNITY
Explore all skills by this author →
GitHub

node-inspect-debugger

Debug Node.js applications using inspector breakpoints and Chrome DevTools Protocol.

Updated Feb 21, 2026
Search Tags:#debugging#nodejs#breakpoints#inspector#runtime analysis#chrome devtools protocol
One-click install
npx skills add https://github.com/Gitnapp/Skills --skill node-inspect-debugger-gitnapp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/Gitnapp/Skills/tree/main/software-development/node-inspect-debugger
Command: npx skills add https://github.com/Gitnapp/Skills --skill node-inspect-debugger-gitnapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers diagnose difficult Node.js runtime issues when logging is insufficient by enabling interactive inspection, breakpoints, stack analysis, and state evaluation.

Core Features & Use Cases

  • Inspector Debugging: Use node inspect and Chrome DevTools Protocol workflows to pause execution, set breakpoints, step through code, and inspect variables.
  • Automated Runtime Analysis: Attach programmatic CDP debugging sessions to collect scopes, evaluate expressions, and capture CPU profiles or heap snapshots.
  • Use Case: Debug a failing Node.js test, inspect a running terminal UI process, or investigate asynchronous behavior by attaching the inspector and examining execution state.

Quick Start

Use the node-inspect-debugger skill to attach a debugger to my Node.js process and help me inspect the failing code path.

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 when console logging is not enough?▼

You can debug Node.js applications using the node inspect command and Chrome DevTools Protocol to pause execution, set breakpoints, and evaluate runtime state. This interactive inspector workflow diagnoses difficult issues when console logging fails to reveal the root cause.

Can I attach a debugger to an already running Node.js process?▼

Yes, you can attach a debugger to a running Node.js process using programmatic Chrome DevTools Protocol sessions. This allows you to inspect active terminal UI processes or investigate asynchronous behavior by evaluating the current execution state without restarting the application.

How do I capture CPU profiles and heap snapshots for Node.js runtime analysis?▼

Capture CPU profiles and heap snapshots by attaching programmatic Chrome DevTools Protocol debugging sessions to your Node.js application. This automated runtime analysis collects diagnostic data to investigate performance issues and memory leaks during execution.

Does Node inspector debugging work for child processes and failing tests?▼

Node inspector debugging supports child process inspection and failing test scenarios. It uses Chrome DevTools Protocol techniques to step through code, manage breakpoints, and evaluate execution state across various Node.js development scenarios.

What is the best way to inspect variables and scopes during Node.js execution?▼

The best way to inspect variables and scopes is using Chrome DevTools Protocol workflows with node inspect. This technique pauses execution at breakpoints, allowing you to evaluate expressions, analyze the call stack, and examine runtime state interactively.

Related Skills

Explore More Software Engineering Skills→
superfhpsuperfhp

node-inspect-debugger

Debug Node.js applications using the V8 inspector and Chrome DevTools Protocol.

Community
Advanced
dogekikidogekiki

system-profile

Profile CPU, memory, GPU, and interconnect metrics for processes.

Community
Advanced
ruiyangruiyiruiyangruiyi

node-inspect-debugger

Attach the Node.js inspector and set breakpoints to debug runtime failures.

Community
Intermediate
pmcdowallpmcdowall

python-debugpy

Debug Python execution failures with pdb and debugpy workflows.

Community
Advanced