Help us improve
Share bugs, ideas, or general feedback.
Auto-discovered marketplace from alonw0/python-debugger-skill
npx claudepluginhub alonw0/python-debugger-skillPyCharm-like Python debugging with breakpoints, stepping, variable inspection, and stack navigation
Open Design — local-first design app exposed to coding agents over MCP. Install once with your agent's plugin command and projects/files/skills are reachable through stdio.
Claude Code plugins for the Slidev presentation framework
Bundled plugins for actuating and debugging the Chrome browser.
Share bugs, ideas, or general feedback.
A Claude Code plugin marketplace containing the Python Debugger plugin - PyCharm-like debugging for Python scripts.
When Claude Code encounters a bug in Python code, it typically resorts to:
This is inefficient. Real developers don't debug this way—they use debuggers.
This skill gives Claude Code the same debugging capabilities that developers use in PyCharm or VS Code:
Faster bug resolution - Instead of guessing and re-running, Claude can pause execution exactly where needed and inspect state directly.
Systematic debugging - The skill includes debugging methodology that teaches Claude to debug like an experienced developer: form hypotheses, verify assumptions, binary search for bugs.
Better accuracy - By actually observing runtime values rather than inferring them from code, Claude makes fewer mistakes when diagnosing issues.
Complex bug handling - Some bugs only manifest at runtime with specific data. Print debugging can't easily catch issues like race conditions, state mutations, or deep call stack problems. A real debugger can.
Without this skill:
User: "This function returns wrong values sometimes"
Claude: *reads code* "I think the issue might be X. Let me add some prints..."
*adds prints, runs, reads output, guesses again*
With this skill:
User: "This function returns wrong values sometimes"
Claude: *sets conditional breakpoint* "Let me pause when the output looks wrong"
*inspects actual variable values at that moment*
"Found it - the input was None here because..."
/plugin marketplace add alonw0/python-debugger-skill
/plugin install python-debugger@python-debugger-marketplace
PyCharm-like Python debugging with breakpoints, stepping, variable inspection, and stack navigation.
Features:
Usage: Just ask Claude Code to debug your Python scripts:
"Debug my_script.py - it's returning wrong values"
"Set a breakpoint at line 25 and inspect the variables"
"Why is this function crashing?"
"Step through the loop and show me what's happening"
python-debugger-skill/
├── .claude-plugin/
│ └── marketplace.json
├── plugins/
│ └── python-debugger/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ └── skills/
│ └── python-debugging/
│ ├── SKILL.md
│ ├── scripts/
│ │ ├── debugger.py
│ │ └── inspector.py
│ └── references/
│ ├── methodology.md
│ ├── commands.md
│ ├── examples.md
│ └── troubleshooting.md
├── examples/
│ └── buggy_calculator.py # Try debugging this!
└── README.md
The repo includes an example buggy script with 3 intentional bugs. After installing the plugin, ask Claude Code to debug it.
python examples/buggy_calculator.py
You'll see incorrect outputs and errors.
Once the plugin is installed, just ask Claude Code naturally:
"Debug examples/buggy_calculator.py - it's crashing on empty lists"
"Help me find why calculate_total_price returns wrong values on the second call"
"Step through process_user_data and figure out why it's missing users"
Claude Code will automatically use the python-debugging skill to:
You: "Debug examples/buggy_calculator.py - the calculate_total_price function returns wrong values"
Claude Code: Uses the debugging skill to:
apply_discountdiscounts list