Skip to main content

/

/

Stats

Actions

Tags

Stats

Actions

Tags

ClaudePluginHub

Community directory for discovering and installing Claude Code plugins.

Find plugins for your project

AI-powered recommendations based on your stack.

Product

Browse Plugins
Marketplaces
Pricing
About
Contact

Resources

Learning Center
Blog
Weekly Digest
Claude Code Docs
Plugin Guide
Plugin Reference
Plugin Marketplaces

Community

Browse on GitHub
Get Support

Legal

Terms of Service
Privacy Policy

Browse · Plugins · Top Plugins · Marketplaces · Components · Technologies · Skills · Agents · Commands · Hooks · MCP Servers · LSP Servers · Output Styles · Themes · Monitors

Categories · Productivity · Development · Testing · Deployment · Security · Documentation · Data · Utilities

© 2025 ClaudePluginHub

Community Maintained · Not affiliated with Anthropic

ClaudePluginHub

ClaudePluginHub

Tools Learn Pricing

Search everything...

diagnose-bug | mcpdebug-plugin

Home
Skills
mcpdebug-plugin
diagnose-bug

Skill

diagnose-bug

From mcpdebug-plugin

Diagnose Python, Node.js, or PHP runtime bugs by driving mcp-debugger after a static execution-risk preflight.

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/mcpdebug-plugin:diagnose-bug

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

1. Inspect the repo and determine whether the target is `python`, `javascript`, or `php`.

SKILL.md

19 lines · ~222 tokens

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Diagnose Bug

Inspect the repo and determine whether the target is python, javascript, or php.
Run the execution-risk-check workflow before any debug session.
If the likely command is obvious from nearby tests or scripts, use it.
If the command is not clear, ask the user for the exact entrypoint or test command.
Use mcp-debugger directly:
- create a debug session for the chosen language
- start debugging with stop-on-entry or a breakpoint near the failure
- inspect stack, scopes, variables, and evaluated expressions
Explain the failure from observed runtime state, not static guesswork.

For PHP, require Xdebug-backed execution. If Xdebug is missing, stop and report the setup requirement.

$

npx claudepluginhub edvintoome/mcpdebug-plugin --plugin mcpdebug-plugin

Similar Skills

skill-creator

153.7k

Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.

17 files

document-skills

View skill-creator