Diagnose software failures with ranked root-cause hypotheses and file:line evidence.
npx skills add https://github.com/ggemba/squad-mcp --skill debug-ggemba
Please help me install this Agent Skill. Skill: debug Source: https://github.com/ggemba/squad-mcp/tree/main/skills/debug Command: npx skills add https://github.com/ggemba/squad-mcp --skill debug-ggemba
It helps you quickly understand why a bug is happening by producing a ranked set of plausible root-cause hypotheses, each tied to specific file:line evidence and a fast verification you can run.
Use the debug skill by running: /squad:debug --normal "500 errors started after the rate-limit change" and include any available stack trace or repro steps after the description.
High-intent search queries and answers about installing and using this skill.
This skill provides read-only debugging by generating ranked root-cause hypotheses for software failures, grounding each cause in specific file:line evidence from code-explorer lookups. It evaluates bug reports alongside available stack traces and repro steps to identify plausible failure causes without making code edits.
The best way to diagnose a 500 error is to run the skill in normal mode with your bug description, stack trace, and repro steps. It analyzes the provided evidence to output a ranked list of plausible root causes, each paired with a single, fast verification check to confirm the issue.
No, this debugging tool strictly enforces read-only operation and never proposes code patches or makes code edits. It focuses solely on diagnosis by providing evidenced root-cause hypotheses and cheap discrimination checks to help you understand the failure before you modify anything.
Yes, you can use this skill to perform read-only codebase reasoning to diagnose failures across quick, normal, and deep investigation modes. It safely analyzes your codebase to generate grounded hypotheses and explicitly labels any speculative items that lack concrete file:line evidence.
To verify a root cause hypothesis quickly, the skill provides a single, cheap discrimination check per hypothesis that is designed to be runnable within about a minute. This fast verification step allows you to confirm or eliminate each plausible cause efficiently during your bug investigation.
himattmWrite a failing Android Kotlin/Java test that reproduces a bug before production changes.
roborewAnalyze bug reports and logs to generate ranked root-cause hypotheses and fix plans.
iiammaeSummarize a codebase by detecting languages, entry points, and dependencies.
chrysaliscatGuide systematic debugging with debuggers, internet search agents, and codebase investigators.
