skills.rest
HugoAlmeidaMoreira
HugoAlmeidaMoreiraCOMMUNITY
Explore all skills by this author →
GitHub

node-inspect-debugger

Debug Node.js apps using --inspect and the Chrome DevTools Protocol.

Updated Aug 27, 2026
Search Tags:#debugging#repl#cdp#nodejs#breakpoints#tui#inspector
One-click install
npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill node-inspect-debugger-hugoalmeidamoreira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/HugoAlmeidaMoreira/zeus-agent/tree/main/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/HugoAlmeidaMoreira/zeus-agent --skill node-inspect-debugger-hugoalmeidamoreira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Node.js applications can be tedious when you rely on logs alone; this skill provides a structured approach to pause, inspect, and control execution using Node's built-in inspector and Chrome DevTools Protocol.

Core Features & Use Cases

  • Interactive debugging with node inspect for quick experimentation and REPL access.
  • Programmatic debugging with Chrome DevTools Protocol (CDP) via chrome-remote-interface for automated breakpoints and state capture in scripts or tests.
  • Attaching to running processes or starting with the inspector to diagnose startup issues, performance bottlenecks, or complex runtime bugs.

Quick Start

Start a Node.js process with --inspect-brk and attach the debugger to begin interactive 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 using the built-in inspector?▼

You debug a Node.js application by starting the process with the --inspect or --inspect-brk flag, which allows you to attach a debugger to set breakpoints, inspect variables, and step through code execution.

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

The Chrome DevTools Protocol (CDP) is used for programmatic debugging in Node.js, enabling automated breakpoints and state capture within scripts or tests via the optional chrome-remote-interface package.

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

Yes, you can attach a debugger to running Node.js server processes to diagnose runtime bugs, performance bottlenecks, or startup issues without needing to restart the application from the beginning.

What is the difference between node inspect and programmatic CDP workflows?▼

Node inspect provides an interactive terminal REPL for quick experimentation, whereas programmatic CDP workflows automate debugging tasks, such as setting breakpoints and capturing state directly within scripts.

Do I need chrome-remote-interface to set breakpoints in Node.js?▼

No, you do not need chrome-remote-interface to set breakpoints; it is an optional dependency used specifically for programmatic CDP scripting, while standard interactive debugging uses the built-in node inspect command.

When should I use --inspect-brk instead of --inspect?▼

You use the --inspect-brk flag instead of --inspect when you need to debug startup issues, as it pauses execution immediately at the first line of code before any scripts run, allowing you to attach the debugger.

Related Skills

Explore More Software Engineering Skills→
AlvaroBianoAlvaroBiano

node-inspect-debugger

Debug Node.js applications via the built-in inspector and Chrome DevTools Protocol.

Community
Intermediate
cardano-foundationcardano-foundation
822

debug

Diagnose Buildkite CI failures by listing builds, inspecting jobs, and fetching logs.

Official
Intermediate
zengbaochengzengbaocheng

node-inspect-debugger

Debug Node.js processes with built-in inspect and Chrome DevTools Protocol.

Community
Intermediate
zeronx798zeronx798

node-inspect-debugger

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

Community
Advanced