From mcpdebug-plugin
Diagnose Python, Node.js, or PHP runtime bugs by driving mcp-debugger after a static execution-risk preflight.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mcpdebug-plugin:diagnose-bugThe 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`.
python, javascript, or php.execution-risk-check workflow before any debug session.mcp-debugger directly:
For PHP, require Xdebug-backed execution. If Xdebug is missing, stop and report the setup requirement.
npx claudepluginhub edvintoome/mcpdebug-plugin --plugin mcpdebug-pluginGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.