“debugging”

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

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

Debug AOTInductor (AOTI) errors and crashes.

Disciplined diagnosis loop for hard bugs and performance regressions.

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…

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

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).

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

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

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

Systematically debug issues with persistent state across context resets.

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

Find the root cause before proposing any fix: reproduce, read the error, diff against what changed, form one hypothesis, test it minimally.

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

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

Help a developer debug a failing Solana program or transaction.

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

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