node-inspect-debugger

Control the Node.js V8 inspector for breakpoints, call-stack inspection, and heap profiling.

9|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill node-inspect-debugger-cyapstaye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/Cyapstaye/Adame_ver.open/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill node-inspect-debugger-cyapstaye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the difficulty of debugging complex Node.js applications where standard logging is insufficient, allowing for deep inspection of state, call stacks, and closures.

Core Features & Use Cases

  • Interactive Debugging: Provides a CLI-based REPL to set breakpoints, step through code, and evaluate expressions in real-time.
  • Programmatic CDP: Enables automated debugging sessions using the Chrome DevTools Protocol to capture heap snapshots, CPU profiles, or state across multiple runs.
  • Use Case: When a TUI component or background worker behaves unexpectedly, use this skill to attach to the process, pause execution at a specific line, and inspect local variables or closure scopes to identify the root cause.

Quick Start

Use the node-inspect-debugger skill to attach to a running Node.js 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 programmatically debug a Node.js application using the Chrome DevTools Protocol?

Programmatic Node.js debugging uses the Chrome DevTools Protocol to interface with the V8 inspector, enabling automated control over breakpoints, heap snapshots, and state analysis for agent-driven workflows.

How do I inspect local variables and closure scopes in a running Node.js process?

Inspect local variables and closure scopes by attaching to a running Node.js process, pausing execution at a specific line via breakpoints, and evaluating expressions in real-time through an interactive REPL.

When do I need deep Node.js inspection instead of standard logging?

Deep Node.js inspection is needed when standard logging is insufficient for debugging complex applications, allowing you to analyze call stacks, closure scopes, and heap state to find root causes in unexpected background workers.

Can I automate capturing CPU profiles and heap snapshots across multiple Node.js runs?

Automated debugging sessions capture CPU profiles and heap snapshots across multiple runs by programmatically driving the Chrome DevTools Protocol to interface with target Node.js processes.

Does node-inspect-debugger require specific dependencies to attach to a process?

Attaching to a process requires access to the Node.js runtime and the Chrome DevTools Protocol to interface with target processes, with no additional external dependencies needed.

What are the limitations of using a CLI-based REPL for Node.js breakpoint management?

A CLI-based REPL for Node.js breakpoint management requires pausing execution at specific lines to evaluate expressions interactively, which may halt background workers and is best suited for deep state analysis rather than production monitoring.