메뉴
Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when debugging API servers, workers, or backend scripts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | node-debugging |
| description | Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when debugging API servers, workers, or backend scripts. |
Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when the user needs to debug API servers, workers, or backend scripts.
This skill activates when:
PLATFORM=node or run node-devtools-mcp separatelydebug_connect)debug_connect with pid)debug_connect with processName)debug_connect with containerName or containerId)For Docker: use host.docker.internal or container name when MCP runs in a container. Mount /var/run/docker.sock in the MCP container.
debug_put-tracepoint): Capture call stack and local variables at code locationsdebug_put-logpoint): Evaluate and log expressionsdebug_put-exceptionpoint): Capture on uncaught or all exceptionsdebug_add-watch): Evaluate at every tracepoint hitdebug_get-probe-snapshots (types: tracepoint, logpoint, exceptionpoint; returns tracepointSnapshots, logpointSnapshots, exceptionpointSnapshots)debug_clear-probe-snapshots — clear when done to free memorydebug_get-logs): Captures console.log, error, warn from the Node processdebug_resolve-source-location): Resolve bundled code to original sourcepage). See commands/node/execute.md.debug_connect with pid, processName, or containerNamedebug_get-probe-snapshots (types: tracepoint, exceptionpoint)page binding)debug_clear-probes, debug_disconnecturlPattern matching script paths (e.g. routes/api.ts, server.js)fromSequence for incremental retrievalAutomated browser testing and debugging using Browser DevTools MCP. Use when testing web pages, debugging frontend issues, verifying UI behavior, or automating browser interactions.
Use when the user wants to run JavaScript in the browser, run code in Node, or batch multiple MCP tool calls. Run script, execute code, batch tools.
Debug web applications by inspecting console logs, network requests, JavaScript errors, and using non-blocking tracepoints/logpoints. Use when debugging web pages, inspecting API calls, or tracing code execution.
Monitor and debug web applications using OpenTelemetry, console logs, network requests, and distributed tracing. Use when correlating frontend and backend requests or debugging request flow across services.
Analyze web page performance using Web Vitals and network timing metrics. Use when optimizing load times, checking Core Web Vitals, or investigating slow pages.
Perform visual testing and UI verification using screenshots and DOM inspection. Use when verifying UI appearance, comparing with designs, or checking for visual regressions.