node-inspect-debugger

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

3|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/DarkArty07/Aether-Agents --skill node-inspect-debugger-darkarty07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/DarkArty07/Aether-Agents/tree/main/home/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/DarkArty07/Aether-Agents --skill node-inspect-debugger-darkarty07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of debugging complex Node.js runtime issues where simple console.log statements cannot access closure variables, async hang points, or pre-render UI state, eliminating guesswork when troubleshooting failing tests, misbehaving terminal interfaces, or long-running background processes.

Core Features & Use Cases

  • Built-in REPL Debugging: Use Node's zero-install node inspect CLI to set breakpoints, step through code, inspect local and closure scope, and evaluate expressions in paused frames for quick troubleshooting.
  • Scriptable CDP Automation: Leverage the Chrome DevTools Protocol via chrome-remote-interface to automate breakpoint setup, collect runtime state across runs, and debug non-interactively from agent loops.
  • Specialized Workflows: Includes pre-defined steps for debugging Hermes ui-tui Ink components, Vitest test runs, and capturing CPU profiles or heap snapshots for performance analysis. Common use cases include troubleshooting failing Node tests, inspecting pre-render React/Ink state, debugging TUI gateway child processes, and diagnosing async code hangs.

Quick Start

Use the node-inspect-debugger skill to attach a debugger to your target Node.js process, set breakpoints at specific code locations, and inspect local variable values when execution pauses to identify the root cause of runtime issues.

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.log cannot access closure variables?

Debug Node.js applications by attaching the built-in V8 inspector to set breakpoints, step through code execution, and inspect local and closure scope variables in paused frames to pinpoint runtime issues without guesswork.

Can I automate setting breakpoints in Node.js non-interactively from an agent loop?

Yes, you can automate breakpoint setup and collect runtime state across runs non-interactively by leveraging the Chrome DevTools Protocol via chrome-remote-interface to script CDP automation for Node.js workloads.

What is the best way to debug failing Vitest test runs in Node.js?

The best way to debug failing Vitest test runs is using the Node.js inspect CLI to attach a debugger, set breakpoints at specific code locations, and evaluate arbitrary expressions in paused frames to identify the root cause.

Does node inspect work for debugging terminal user interfaces built with Ink?

Yes, Node.js inspect supports debugging Hermes ui-tui Ink components by allowing you to set breakpoints and inspect pre-render React and Ink state to troubleshoot misbehaving terminal user interfaces.

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

Capture CPU profiles and heap snapshots for performance analysis by attaching the V8 inspector to your Node.js process via the Chrome DevTools Protocol, enabling detailed runtime profiling for your workloads.

Do I need external dependencies to inspect async code hangs in long-running background processes?

No external dependencies are required, because this Skill uses Node's zero-install built-in inspect CLI and the V8 inspector to diagnose async code hangs and debug long-running background processes.