node-inspect-debugger

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

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/ghufronbagaskara/agent-im --skill node-inspect-debugger-ghufronbagaskara
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/ghufronbagaskara/agent-im/tree/main/hermes-home/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/ghufronbagaskara/agent-im --skill node-inspect-debugger-ghufronbagaskara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves complex runtime issues in Node.js applications by providing a structured approach to interactive debugging, call-stack analysis, and state inspection when standard logging is insufficient.

Core Features & Use Cases

  • Interactive Debugging: Utilize the built-in node inspect REPL for real-time breakpoint management, step-by-step execution, and variable evaluation.
  • Advanced CDP Integration: Leverage the Chrome DevTools Protocol for non-interactive, automated debugging, heap snapshotting, and CPU profiling.
  • Use Case: When a TUI gateway or background worker behaves unexpectedly, use this skill to attach to the running process, set breakpoints in the source code, and inspect closure variables or React/Ink state to identify the root cause.

Quick Start

Use the node-inspect-debugger skill to attach to the running process with PID 1234 and set a breakpoint at line 42 of the main application file.

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 the V8 inspector?▼

Debug Node.js applications using the V8 inspector by attaching to running processes, setting breakpoints in source code, and evaluating variables interactively via the node inspect REPL for real-time state inspection.

What is the best way to analyze memory leaks in Node.js?▼

Analyze memory leaks in Node.js by leveraging Chrome DevTools Protocol integration for non-interactive automated debugging and capturing heap snapshots to identify retained objects and complex asynchronous workflow issues.

How do I attach a debugger to a running Node.js background worker?▼

Attach a debugger to a running Node.js background worker by targeting its process ID, setting breakpoints in the source code, and inspecting closure variables or React/Ink state to identify the root cause of unexpected behavior.

Does the Chrome DevTools Protocol support CPU profiling for Node.js?▼

The Chrome DevTools Protocol supports CPU profiling for Node.js by enabling non-interactive, automated debugging sessions that capture performance metrics and analyze complex asynchronous workflows.

When should I use interactive CLI debugging instead of standard logging in Node.js?▼

Use interactive CLI debugging instead of standard logging in Node.js when standard logging is insufficient and you need structured call-stack analysis, deep-dive troubleshooting, and programmatic state inspection for complex runtime issues.