Favicon of node-inspect-debugger

node-inspect-debugger Skill

AI Agent SkillPythonOpen source

Debug Node.js via --inspect + Chrome DevTools Protocol CLI. Published by NousResearch in hermes-agent.

What is node-inspect-debugger Skill?

Debug Node.js via --inspect + Chrome DevTools Protocol CLI. Published by NousResearch in hermes-agent. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
100/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Testing
  • Design and media
  • Testing use cases
  • Design and media use cases

Technical details

Copy skill directory
  • Install or run with Copy skill directory

When to use node-inspect-debugger Skill

  • Use it for testing.
  • Use it for design and media.

Built with

PythonCopy skill directory

Editorial notes

Source

  • Creator: NousResearch
  • Repository: NousResearch/hermes-agent
  • Skill file: skills/software-development/node-inspect-debugger/SKILL.md

What it does

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

Skill instructions

Node.js Inspect Debugger Overview When console.log isn't enough, drive Node's built-in V8 inspector programmatically from the terminal. You get real breakpoints, step in/over/out, call-stack walking, local/closure scope dumps, and arbitrary expression evaluation in the paused frame. Two tools, pick one: - node inspect — built-in, zero install, CLI REPL. Best for quick poking. - ndb / CDP via chrome-remote-interface — scriptable from Node/Python; best when you want to automate many breakpoints, collect state across runs, or debug non-interactively from an agent loop. Prefer node inspect first. It's always available and the REPL is fast. When to Use - A Node test fails and you need to see intermediate state - ui-tui crashes or behaves wrong and you want to inspect React/Ink state pre-render - tuigateway child processes (SlashWorker, PTY bridge workers) misbehave - You need to inspect a value in a closure that console.log can't reach without patching - Perf: attach to a running process to

Explore related resources

Frequently asked questions

What is node-inspect-debugger?

node-inspect-debugger is a open-source AI agent skill with Copy skill directory. Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

Who is node-inspect-debugger best for?

node-inspect-debugger is best for reusing agent instructions, scripts, and references, testing workflows, design and media workflows.

How do I install node-inspect-debugger?

Install or run node-inspect-debugger using Copy skill directory. Check node-inspect-debugger for the latest setup command.

Is node-inspect-debugger actively maintained?

node-inspect-debugger may need a closer maintenance check before production use.

Share:

Stars
214,436
Forks
39,858
Last commit
9 days ago
Repository age
1 year
License
MIT

Auto-fetched from GitHub.

Ad
Favicon

 

  
 

Similar to node-inspect-debugger