“Debugging”

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

Systematic debugging workflow: reproduce, minimize, hypotheses, instrument, fix, prevent, verify.

버그, 테스트 실패, 예상 밖 동작을 수정하기 전에 근본 원인을 조사할 때 사용한다.

Gates test-only code behind one literal TEST_ONLY switch: debug menu, debug link, simulated clock and offline.

Diagnose DNS resolution failures in the cluster (NXDOMAIN, timeouts, SERVFAIL).

Systematic debugging with persistent state across context resets

Use when debugging a bug you can't yet reproduce reliably, or when you need a tight/automated reproduction loop before hypothesising — especially…

Finds the cause by evidence, proves it, fixes it.

Use when a check fails: a red test, a broken build, a failed clause, or a bug you can point at.

AI-powered mobile device automation for Android and iOS devices, emulators, and simulators

Run a structured debugging workflow from symptom to validated root cause.

Use when diagnosing OpenClaw provider, tool-surface, code-mode, streaming, transcript, worker or package-runtime failures.

Diagnose and fix a reproducible failure in an existing project.

Diagnose pod scheduling failures (Pending, Unschedulable).

Stream real-time debug events from the Vocal Bridge voice agent.

Structured self-debugging workflow for AI

Guides systematic root-cause debugging.

Four-phase debugging framework that finds root causes before attempting fixes.

Structured debugging — reproduce, diagnose, fix with @omg:debugger agent

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

Guides systematic root-cause debugging.

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

Diagnose Emacs hook ordering, key binding shadowing, remaps, and advice-related behavior.

Systematic root-cause isolation for test failures, runtime errors, or unexpected behavior.