node-inspect-debugger

Debug Node.js applications programmatically via the inspector protocol and CDP.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill node-inspect-debugger-anandaanugrahhandyanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill node-inspect-debugger-anandaanugrahhandyanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug Node.js applications by using the built-in inspector and Chrome DevTools Protocol from the terminal, enabling breakpoints, stepping, scope inspection, and on-demand evaluation when logging alone isn't enough.

Core Features & Use Cases

  • Terminal-based debugging with node inspect and CDP scripting to automate common debugging tasks
  • Attach to a running process or start with --inspect/--inspect-brk to pause on entry
  • Inspect local and closure scope, walk the call stack, and evaluate expressions in paused frames

Quick Start

Launch your target with node --inspect-brk script.js to pause on entry and attach with node inspect to begin debugging.

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 from the terminal using breakpoints?

Debug Node.js applications from the terminal by launching scripts with --inspect-brk and attaching via node inspect to set breakpoints, step through code, and evaluate expressions in paused frames.

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

Yes, you can attach a debugger to a running Node.js process by using the inspector protocol and CDP scripting to pause execution, inspect local and closure scope, and walk the call stack.

What is the Chrome DevTools Protocol used for in Node.js debugging?

The Chrome DevTools Protocol enables programmatic, breakpoint-driven debugging of Node.js applications, allowing you to automate debugging tasks, inspect state, and evaluate expressions on demand across CLI and CDP tooling.

Does Node.js inspector debugging work on Windows and macOS?

Yes, Node.js inspector debugging works across Linux, macOS, and Windows, requiring only a Node.js version with inspector support and optional wiring to chrome-remote-interface for CDP scripting.

When should I use the node inspect tool instead of adding console logs?

Use the node inspect tool when logging is insufficient and you need to pause execution on entry, inspect closure scope, walk the call stack, and interactively evaluate expressions in paused frames.

Can I automate Node.js debugging tasks in CI workflows?

Yes, you can automate debugging tasks in CI workflows by using the inspector protocol and CDP scripting to programmatically pause execution, inspect state, and evaluate expressions without manual terminal interaction.