“Debugging”

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

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.

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…

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.

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…

Interactive debugging workflow with hypothesis-driven probe loop.

Structured debugging runbook for backend services.

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

Evidence-driven embedded Linux Wi-Fi debugging using logs, packet captures, iw, iwinfo, iwpriv, ip, ethtool, netlink, socket statistics, driver/firmware logs…

Improve Plano tracing and debugging workflows.

Debug cross-platform process, shell, sandbox, pipe, handle, startup, and shutdown behavior.

Systematic debugging methodology — reproduce, isolate, hypothesize, fix, verify.

Systematic debugging including profiling tools, log analysis, bisection technique, and production debugging.

Debug end to end with swarm verification — clarify intent vs observed, check the feature's spec for the gap that let it slip, trace the data path, attribute…

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

Comprehensive debugging methodology for finding and fixing bugs (formerly debugging).

Debugging patterns and workflows for CSS layout, stacking, paint, and rendering issues.