“debugging”

Use the moment any test fails twice, when a build breaks unexpectedly, when the code-reviewer rejects code, when the implementer reports BLOCKED, when the…

Structured debugging with mandatory evidence gathering before any fix attempt.

Expert debugging methodology.

Create debugging tools for AI behavior visualization and analysis

Beginner-friendly reverse-engineering workflow for Systematic Debugging.

Instrument a C# codebase with exhaustive temporary debug logging to capture runtime behavior across complex, high-iteration execution flows.

Fix bugs using Dan Abramov's systematic debugging method.

Systematically find root causes and fix bugs.

Diagnoses and resolves memory leaks in JavaScript/Node.js applications.

Debug experiment code with structured error analysis.

Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.

Android diagnosis workflow for crashes, ANRs, incorrect UI state, coroutine or Flow bugs, data loading failures, and Compose rendering issues.

Run the st-debug agent on demand for one task of the current feature, then verify with st-verify.sh (test green, no added comment lines).

Analyze errors and debug output to find root causes

Systematic debugging - hypothesis and symptom tracked in a state file that survives /clear, with a user-gated second-model consult at dead ends

Chrome DevTools MCP ile browser debugging.

Debug a Tendril plan by analyzing its execution logs, session JSONL, verification results, and checking infrastructure.

Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests.

Systematic debugging expertise - 4-phase root cause process, evidence gathering, and hypothesis testing.

Debugs failures using reproduce-isolate-fix-verify steps instead of random changes.

Launch ephemeral debug container in running pod for interactive debugging.

Use when the user asks to debug, diagnose, reproduce, or fix a hard bug, flaky failure, crash, incorrect result, or performance regression.

Use when diagnosing a bug, failing check, unexpected behavior, or production incident before changing code.

Systematically debug issues with persistent state across context resets.