Debugging
Find and fix bugs, error analysis
Uses and selection guide
Use these skills to move from a reproducible issue or change request to a reviewable patch. Match the language, framework and test runner to your repository; compare the proposed diff and run your own checks before accepting edits.
debug
by Terryc21
'Systematic debugging workflow: reproduce, isolate, hypothesize, verify, fix. Triggers: "debug", "find bug", "fix crash", "why is this broken", "not working".'
scan-similar-bugs
by Terryc21
'After fixing a bug, systematically find other instances of the same pattern. Triggers: "scan for similar bugs", "find other instances", "check for similar issues", "scan similar bugs".'
render-debug
by render-oss
Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.
verification-before-completion
by bobmatnyc
Run verification commands and confirm output before claiming success
systematic-debugging
by bobmatnyc
Methodical debugging instead of random changes
mcp-debug
by TechNickAI
"Use when testing MCP servers, debugging MCP tool responses, exploring MCP capabilities, or diagnosing why an MCP tool returns unexpected data"
systematic-debugging
by TechNickAI
"Use when debugging bugs, test failures, unexpected behavior, or needing to find root cause before fixing"
verification-before-completion
by bobmatnyc
Run verification commands and confirm output before claiming success
chrome-devtools
by arlenagreer
Chrome debugging and inspection via local CDP Docker container
mcp-developer
by Jeffallan
Use when building, debugging, or extending MCP servers or clients that connect AI systems with external tools and data sources. Invoke to implement tool handlers, configure resource providers, set up stdio/HTTP/SSE transport layers, validate schemas with Zod or Pydantic, debug protocol compliance issues, or scaffold complete MCP server/client projects using TypeScript or Python SDKs.
docker-management
by NousResearch
Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization.
debug-local
by lightdash
Debug the Lightdash app using PM2 logs, Maple traces, and browser automation. Use when investigating issues, tracking down bugs, understanding request flow, or correlating frontend actions with backend behavior.
cc-safety-net
by kenryu42
"Operate CC Safety Net: explain why a command was blocked, triage false positives, configure custom rulebooks, manage agent CLI integrations, and diagnose protection."
sentry-javascript-bugs
by getsentry
'Review Sentry React and TypeScript changes for bug patterns drawn from real production issues. Use when reviewing a frontend diff or PR, checking Warden findings, auditing the current branch, reviewing production-error patterns, or looking for common regressions in static/.'
troubleshoot
by microsoft
Investigate unexpected chat agent behavior by analyzing direct debug logs in JSONL files. Use when users ask why something happened, why a request was slow, why tools or subagents were used or skipped, or why instructions/skills/agents did not load.
flaky-smoke-tests
by microsoft
Diagnose intermittent VS Code Electron smoke-test failures from the Azure DevOps Flaky Smoke Tests pipeline (definition 700). Covers finding failed iterations, downloading task logs and platform artifacts with Azure CLI, correlating cumulative runner logs, tracing the introducing commit, and queueing focused validation runs.
otel
by microsoft
OpenTelemetry instrumentation for the Copilot Chat extension — covers the four agent execution paths, the IOTelService abstraction, span/metric/event conventions, and the relationship between code and the user/developer monitoring docs. Use when adding/changing OTel spans, metrics, or events; instrumenting a new agent surface; touching the Copilot CLI bridge or Claude span emission; or updating extensions/copilot/docs/monitoring/agent_monitoring*.md.
heterogeneous-agent
by lobehub
'Implement or debug LobeHub heterogeneous agents. Use for Claude Code/Codex adapters, external CLI agents, event mapping, IPC, persistence, tool-call chains, sessions, traces, or adapter bugs.'
agent-runtime-hooks
by lobehub
'Agent runtime lifecycle hooks. Use for before/after tool or step hooks, tool mocks, human intervention, sub-agent calls, context compression, evals, callAgent, or lifecycle events.'
debug-frontend-with-browser
by lobehub
Frontend diagnosis extension for the acceptance skill. Use for intermittent rendering, ordering, stale-state, navigation, virtual-list, React/Zustand, optimistic-update, refresh-dependent, or browser-only failures where the first broken boundary may be DOM, component input, derived state, client cache, network data, or a pure transformation. Before any browser, Electron, or live-app interaction, this skill must load and follow the acceptance skill and the repository's .agents/acceptance/ project layer; it adds only boundary tracing, minimal fixture replay, and regression attribution.
five-whys
by wesammustafa
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
Claude-Code-Everything-You-Need-to-Know
by wesammustafa
Find the root cause of a bug by asking why five times
workflows:compound
by brycewang-stanford
Document a recently solved research problem to compound methodological knowledge
pr-build-status
by dotnet
"Retrieve and analyze Azure DevOps build failures for GitHub PRs. Use when CI fails. CRITICAL: Collect ALL errors from ALL platforms FIRST, write hypotheses to file, then fix systematically."