Diagnose errors and regressions using local command outputs, code, and external evidence.
npx skills add https://github.com/sydasif/web-search-mcp --skill debug-sydasif
Please help me install this Agent Skill. Skill: debug Source: https://github.com/sydasif/web-search-mcp/tree/main/skills/debug Command: npx skills add https://github.com/sydasif/web-search-mcp --skill debug-sydasif
Debugging is a complex process where developers need to move from failing commands to root causes using a local-first workflow that combines Context7, GitHub CLI, and Web Search MCP to gather evidence and external references.
Reproduce the error locally, capture the full command output and environment, and consult Context7, GitHub CLI, and Web Search MCP for evidence.
High-intent search queries and answers about installing and using this skill.
Debugging a failing command involves reproducing the error locally and capturing the exact command output. You then gather evidence from local code, tests, and external signals using Context7, GitHub CLI, and Web Search MCP to isolate the root cause.
Tracing a regression locally requires capturing the exact command output and consulting git history. You use Context7 for documentation, GitHub CLI for issue history, and Web Search MCP for external references to validate the root cause and fix.
Yes, you can reproduce flaky tests by running them locally to capture exact outputs. GitHub CLI provides repo metadata and issue history, while Web Search MCP fetches external references to help isolate environmental factors causing the flakiness.
Yes, a local git repository is required to diagnose errors. The workflow is local-first, relying on local code, tests, and exact command outputs to gather evidence and validate fixes before consulting external documentation surfaces.
Evidence-based debugging with Context7 works by gathering factual signals from documentation to support root cause analysis. You start with exact local command outputs, then query Context7 for docs to validate hypotheses and guide your fix.
Your debugging workflow may fail to isolate the root cause if you skip capturing exact command outputs or neglect external signals. Combining local code inspection with GitHub CLI issue history and Web Search MCP references ensures comprehensive evidence gathering.
ChegginConfigure MCP servers via claude mcp add and verify with claude mcp list.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
Simon-Copilot-StudioIdentify root causes of bugs and failures through a four-phase debugging workflow.
cosmixDiagnose and resolve software bugs across programming languages and environments.
