Debug a WRONG or imperfect render (not a hard error) by inspecting inputs and intermediate steps with run-to-node — render one branch up to an output, preview-tap…
解完非平凡 bug 後主動萃取除錯知識的儀式：產出 debug report Markdown、 清理本次留下的過渡產物（註解舊碼、散落 console.log）、封存未採用的實驗方案、 將摘要寫入 ~/.agents/debugs/debug-reports.jsonl，最後提醒手動 /clear。 觸發關鍵字：/debug_report、debug…
Диагностика проблем Revit-плагина — не загружается, не собирается, команда не видна, ошибка addin. Использовать когда студент пишет «не работает», «не видно», «ошибка сборки».
Use when fixing a bug or analyzing a stack trace. Enforces systematic debugging methodology to prevent shotgun debugging and verify fixes.
Debug Python code execution failures by capturing partial traces, isolating failing functions, and incrementally verifying outputs
Monitor, triage, fix, and proactively enhance Sentry error monitoring for any project. Use when asked to: check Sentry, fix Sentry errors, triage Sentry issues, run post-deploy…
마이크로서비스 디버깅 및 로그 분석. Use when: (1) 서비스 에러 분석, (2) 로그 확인, (3) 헬스체크 실패 원인 파악, (4) DB 연결 상태 확인, (5) 환경변수 검증.
Persistent debugging with multi-session state, binary search support, and error pattern matching.
Diagnoses and recovers from complex REST and GraphQL API failures. Enforces reproduction before fixing and verifies via runtime inspection.
Systematic error debugging with analysis, solution discovery, and verification
디버깅, 디버그, 버그, 에러, 오류, 버그 수정 - Specialized in identifying root causes of bugs, analyzing error logs, and providing robust fixes.
버그·오류·예상과 다른 동작이 보고될 때, "디버깅 도와줘", "버그 찾아줘", "에러가 나", "왜 안 되지", "debug" 표현이 있을 때 활성화됩니다. 수행 내용: 재현 조건 확인 → 원인 가설 수립 → 검증 순서 정의의 체계적 디버깅 플레이북을 실행합니다.
Debug stuck Hawk/Inspect AI evaluations. Use when user mentions "stuck eval", "eval not progressing", "eval hanging", "samples not completing", "eval set frozen", "runner stuck",…
Systematically diagnose unclear product behavior or root cause by building a feedback signal, testing one hypothesis at a time, and verifying the original symptom.
Debug agent task execution infrastructure issues — wrong cwd, wrong files, wrong venv, browser startup failures, agent retry loops, skill loading failures
Automates Tauri WebView debugging using official plugins (tauri-plugin-log + screenshots) with process verification, automated screenshots, console logs, and state analysis.
Debug and diagnose Thread mesh networks and OpenThread Border Routers. Use when troubleshooting Thread connectivity, analyzing Router Advertisements, testing IPv6 reachability to…
Use whenever something is broken, flaky, or behaving unexpectedly — find the root cause systematically (reproduce, isolate, hypothesize, verify) and fix the cause, not the…
Diagnose failure modes by systematically investigating traces. Trigger when the user explicitly asks for cross-trace diagnosis: "what's going wrong?", "were there errors?", "debug…
· Triage a live incident to localize an unknown failing layer, then route. Triggers: incident, outage, triage, production down, crashloop, 502.
Systematic debugging approach for Rust async code with Tokio, Turso, and redb. Use when diagnosing runtime issues, performance problems, async deadlocks, database connection…
Video-based visual debugging — extract key frames from screen recordings and analyze UI bugs over time.
Find and connect to IONOS Cloud debugging VMs provisioned with the debug-vm tool. Use when the user wants to deploy to, test on, SSH into, or check status of their debug VMs.
Deploys to
[email protected] VPS and iteratively debugs until successful. Use when deploying to VPS, debugging deployment failures, investigating container issues,…
Guide PMs through debugging AI-generated code: how to read error messages, form effective debugging prompts, isolate issues, and decide when to fix forward vs start over.
Structured diagnostic workflow for debugging application issues using Grafana observability data. Use when the user reports errors, latency spikes, service degradation, HTTP 500s,…
Debug E2E tests by taking screenshots at key points to visually inspect application state.
Debug crashes, segfaults, and memory errors using valgrind integration with nextest through pre-configured profiles
Guides developers through scenario test debugging using Ruby debug gem step execution. Provides interactive debugging patterns and test helper context.
Diagnose covered x402 v2 failures and compare supplied requirements or facilitator capabilities without handling wallet secrets.
Debug broken Zoom implementations quickly. Use when auth, webhooks, SDK joins, MCP transport, or real-time media workflows are failing and you need to isolate the layer before…
Systematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, troubleshooting bugs, investigating crashes, analyzing stack…
Use when debugging complex issues involving multiple modalities (frontend + backend, API + UI, terminal + browser).
Expert at advanced debugging and root cause analysis. Use when troubleshooting complex issues, finding root causes of bugs, investigating performance problems, or analyzing system…
Diagnoses Qdrant production issues using metrics and observability tools. Use when someone reports 'optimizer stuck', 'indexing too slow', 'memory too high', 'OOM crash', 'queries…
Four-phase debugging framework that ensures root cause identification before fixes. Use when encountering bugs, test failures, unexpected behavior, or when previous fix attempts…
Systematically debug code issues using proven methodologies. Use when encountering errors, unexpected behavior, or performance problems.
Use when an Agent2 agent returns errors, 500s, mock data unexpectedly, fails to start, or behaves incorrectly — systematic diagnosis for framework issues, config problems, Docker…
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error.
Investigate a bug or unexpected behavior, find the root cause, write a failing test that reproduces it, then fix and guard.
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and…
Use when troubleshooting Atmos configuration, deployment errors, or unexpected behavior. Covers debug logging, describing stacks/components, interpreting errors, and common issues…
Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Troubleshooting guide for Claude Code issues. Use when Claude behaves unexpectedly, tools fail, sessions hang, or you need to diagnose problems.
Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate…
A reasoning pattern for diagnosing and fixing bugs that span multiple abstraction layers in complex systems.
Debugs and fixes dbt errors systematically. Use when working with dbt errors for: (1) Task mentions "fix", "error", "broken", "failing", "debug", "wrong", or "not working" (2)…
Runtime-instrumentation debugging for bugs that static reading can't pin down — add temporary unconditional JSONL logging to the real code path, reproduce, read the log, then fix.
Debugs Docker build failures, container runtime errors, platform architecture issues (ARM64/AMD64/WSL2), AWS ECR/ECS pull failures, and optimizes Docker workflows.
Expert in systematic debugging, root cause analysis, profiling, and performance troubleshooting. Use when stuck on bugs, investigating errors, or optimizing performance.
Covers debugging Friday agent behavior — local debugging with atlas CLI and remote debugging via GCS logs.
Systematic debugging workflow with root cause analysis and fix verification. Use when user says "debug", "fix bug", "troubleshoot", or "root cause".
Use when diagnosing Eclipse SUMO, TraCI, netconvert, duarouter, route, demand, detector, traffic-light, output, teleport, insertion, seed, performance, or reproducibility failures…
Debug iOS apps and profile performance using LLDB, Memory Graph Debugger, and Instruments. Use when diagnosing crashes, memory leaks, retain cycles, main thread hangs, slow…
Systematically debug issues with reproduction steps, error analysis, hypothesis testing, and root cause fixes.
Use when investigating Kubernetes pod failures, crashes, resource issues, or service degradation. Provides systematic investigation methodology for incident triage, root cause…
Debugs AWS Lambda function timeout failures by systematically analyzing function configuration, CloudWatch logs and metrics, VPC/networking, cold starts, memory constraints, and…
Parse error logs, stack traces, and crash reports into a structured root cause diagnosis. Use when an application is throwing exceptions, crashing, or producing unexpected errors…
Systematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken,…