node-inspect-debugger

Debug Node.js applications via Chrome DevTools Protocol with breakpoints and variable inspection.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LynxLabVN/office-agent --skill node-inspect-debugger-lynxlabvn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-inspect-debugger
Source: https://github.com/LynxLabVN/office-agent/tree/main/agent-core/skills/software-development/node-inspect-debugger
Command: npx skills add https://github.com/LynxLabVN/office-agent --skill node-inspect-debugger-lynxlabvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chrome-remote-interface, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines Node.js debugging by leveraging the Chrome DevTools Protocol (CDP) through CLI commands, allowing developers to step through code, set breakpoints, and inspect variables efficiently.

Core Features & Use Cases

  • Console Replacement: Provides a more robust debugging experience beyond console.log.
  • CLI Integration: Enables debugging from the command line without a graphical interface.
  • Automated Tasks: Executes scripts and processes for automated debugging scenarios.
  • Use Case: When debugging complex Node.js applications, use this Skill to attach to a running process, set breakpoints, and inspect variables and states interactively.

Quick Start

Debug your Node.js application by running 'node inspect path/to/your/script.js' and then set a breakpoint at 'path/to/your/script.js:42'.

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 command line?

To debug a Node.js application from the command line, run 'node inspect path/to/your/script.js' to attach the Chrome DevTools Protocol and interactively step through your code.

Can I set breakpoints and inspect variables in Node.js without a GUI?

Yes, you can set breakpoints and inspect variables without a GUI by using the 'node inspect' command, which leverages the Chrome DevTools Protocol for a robust CLI debugging experience.

What is the best way to replace console.log for debugging complex Node.js applications?

The best way to replace console.log for debugging complex Node.js applications is using Chrome DevTools Protocol via CLI to interactively set breakpoints and inspect application states.

Does Node.js CLI debugging support automated scriptable debugging tasks?

Yes, Node.js CLI debugging supports automated tasks by optionally using the 'chrome-remote-interface' dependency to execute scripts and process automated debugging scenarios programmatically.

How do I attach a debugger to a running Node.js process to inspect states?

You can attach a debugger to a running Node.js process by utilizing the Chrome DevTools Protocol, allowing you to set breakpoints and inspect variables interactively during execution.

Do I need chrome-remote-interface to use the node inspect command?

No, you do not need 'chrome-remote-interface' for basic CLI debugging, but it is required optionally when you want to execute scripts for automated debugging scenarios.