By pzep1
Instrument JavaScript code in Claude Code with fetch calls to a bundled local Node.js debug server, capturing runtime data to debug async issues, race conditions, state changes, and control flow during execution.
Runtime debugging for Claude Code via instrumented fetch calls.
npx skills add pzep1/claudecode-debug-mode
claude plugin marketplace add pzep1/claudecode-debug-mode
claude plugin install claude-debug-plugin@pzep1-claudecode-debug-mode
npx skills add ./claudecode-debug-mode
Claude automatically uses this skill when you ask to debug runtime issues:
scripts/debug-server.jsfetch() calls at strategic locations.claude-debug/debug.log to identify the problem.claude-debug/Claude inserts fetch calls like this:
fetch("http://localhost:3333/debug", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ label: "function-entry", data: { arg1, arg2 } }),
}).catch(() => {});
claudecode-debug-mode/
├── .claude-plugin/
│ ├── marketplace.json
│ └── plugin.json
├── scripts/
│ └── debug-server.js
└── skills/
└── runtime-debugging/
└── SKILL.md
MIT
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBuild and manage iOS/macOS apps using native xcodebuild and xcrun simctl CLI tools. Replaces XcodeBuildMCP with direct CLI commands and XCUITest for UI automation.
npx claudepluginhub pzep1/claudecode-debug-mode --plugin claude-debug-pluginAsk Claude Code to help you debug an issue
Systematically debug issues with step-by-step troubleshooting approaches.
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Systematic debugging and root cause analysis framework - four-phase investigation process ensuring understanding before fixes
Editorial "Web Designer" bundle for Claude Code from Antigravity Awesome Skills.