skills.rest
heysuhas
heysuhasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

node-inspect-debugger

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

2|1|Updated Jul 14, 2026
Search Tags:#debugging#cdp#nodejs#breakpoints#tui#inspector
One-click install
npx skills add https://github.com/heysuhas/hermes_cli --skill node-inspect-debugger-heysuhas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/heysuhas/hermes_cli/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/heysuhas/hermes_cli --skill node-inspect-debugger-heysuhas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface.

What problem does it solve?

This skill resolves complex runtime issues in Node.js applications by providing deep visibility into execution state, call stacks, and variable scopes that standard logging cannot capture.

Core Features & Use Cases

  • Interactive Debugging: Perform step-by-step execution, set breakpoints, and inspect closures or local variables using the built-in V8 inspector.
  • Programmatic Control: Automate debugging sessions and capture heap snapshots or CPU profiles using the Chrome DevTools Protocol.
  • Use Case: When a TUI component or gateway service behaves unexpectedly, use this skill to pause execution at a specific line, inspect the React/Ink state, and evaluate expressions in the current scope to identify the root cause.

Quick Start

Use the node-inspect-debugger skill to attach to a running Node.js process by its PID and set a breakpoint at a specific line in your source 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 Chrome DevTools Protocol?▼

Debug Node.js applications by leveraging the V8 inspector and Chrome DevTools Protocol to interactively manage breakpoints, analyze call stacks, and inspect variable scopes during local development.

Can I attach a debugger to a running Node.js process and inspect its state?▼

Yes, you can attach to a running Node.js process by its PID to pause execution at a specific line, inspect closures, evaluate expressions, and identify runtime issues in complex processes.

How do I capture heap snapshots and CPU profiles for Node.js performance profiling?▼

Capture heap snapshots and CPU profiles through programmatic control of the Chrome DevTools Protocol, enabling non-interactive performance profiling and advanced diagnostic tasks for your applications.

Does this debugging approach work with TUI components and gateway services?▼

Yes, this debugging approach supports advanced diagnostic tasks for complex TUI and gateway processes, allowing you to inspect React/Ink state and evaluate expressions in the current scope.

What is the best way to inspect local variables and closures during Node.js runtime?▼

Interactive debugging with the built-in V8 inspector provides deep visibility into execution state, call stacks, and local variables that standard logging cannot capture during step-by-step execution.

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

Yes, chrome-remote-interface is required as a dependency to automate debugging sessions, programmatically control the V8 inspector, and capture diagnostic snapshots via the Chrome DevTools Protocol.

Related Skills

Explore More Software Engineering Skills→
projectedanxprojectedanx
1

node-inspect-debugger

Control the Node.js V8 inspector for breakpoints, call stacks, and profiling.

Community
Advanced
KaakatiKaakati
2

performance-profiler

Diagnose performance bottlenecks across Rails, PostgreSQL, Redis, Sidekiq, React Native, and Centrifugo.

Community
Advanced
KonghaYaoKonghaYao
5

tui-development

Build terminal user interfaces with React and Ink.js.

Community
Intermediate
zeronx798zeronx798

node-inspect-debugger

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

Community
Advanced