“debugging”

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async…

Deep static analysis and bug hunting for any codebase.

Go debugging skill for delve setup, race condition detection, goroutine tracking, and panic diagnosis.

Structured debugging runbook for backend services.

Use when a CI/test failure seems to have one cause but the real root is different, or when a silent failure hides the real issue.

Advanced debugging assistance and error analysis.

debug this, fix this bug, why is this failing, investigate error, trace the issue, something is broken, test failure, systematic debugging, diagnose, root…

Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb.

Debug REST, GraphQL, webhook, and OAuth/API-key integrations with layered request, auth, schema, and response checks.

Launch ephemeral debug container in running pod for interactive debugging.

This skill should be used when debugging frontend/UI bugs that need runtime evidence.

Metodologia de debugging sistemático para Python, FastAPI, Playwright e Railway.

REQUIRED when diagnosing, troubleshooting, or debugging Pi Coding Agent (`pi`) issues, including provider errors, model catalog refresh failures, HTTP 403/401…

Help a developer debug a failing Solana program or transaction.

难 Bug 的诊断循环：先造出能变红的回路，再谈假设。

When you get a failed result/error/user says its wrong/its a bug, use this skill to systematically debug and fix the problem.

Systematic evidence-based debugging using runtime logs.

Debug or verify frontend behavior by driving a live page (DOM, storage, network, console) with the browser_* tools instead of reading source or asking the…

Troubleshoot ChainGPT API errors and issues.

Diagnosis loop for hard bugs and performance regressions.

Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues.

Debug or verify a local UI end to end in the user's existing Chrome tab, with temporary runtime probes and a manual browser fallback.

Runs a structured production-incident investigation that forces evidence-first hypothesis ranking before any code change.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes