“debugging”

Use for diagnosing bugs, tracing failures, reproducing issues, and isolating root causes.

Structured root-cause investigation for bugs and failures.

Use when a test, build, tool call, or runtime behavior fails and the root cause is not known.

The house debugging discipline for a bug or unexpected behaviour: reproduce it on demand, form one testable hypothesis, isolate the cause with evidence…

Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running…

Zig debugging skill.

Codex debugging: codex-rs core/tui/exec/cli/app-server/config.

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious.

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines.

[ARCHIVED v0.1.0 — superseded by build-loop:debug-loop] Older source-tracked copy of the iterative debug loop, retained for version history.

Debug logging, Debug menu, runtime pitfalls, typing-latency-sensitive paths, SwiftUI list snapshot boundaries, OS-version repros, and local visual iteration…

Guide for debugging issue on a specific code sections, pattern, or files.

Debug Nim compile failures, crashes, wrong results, macro expansion, ownership behavior, and unsafe-memory defects using focused reproduction, stack traces…

Debug OpenClaw model/provider/tool-surface/code-mode/streaming and live/Crabbox behavior; choose logs, probes, proof path before code changes; fetch stored…

Teaches systematic debugging methodology — reproduction, isolation, hypothesis formation, and independent problem-solving — rather than handing out quick fixes.

Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.

Structured debugging methodology — use before proposing fixes for any error or failure.

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

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack.

Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call…

Structured debugging runbook for backend services.

Debugging Expert delivers production-grade technical work with clear architecture, tests, maintainability, and operational awareness.

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.

Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging…