Manage low-power Debian home server (laptop, closed) with 100% containerization, minimal energy footprint, and pristine host OS.
GitHub Actions のワークフロー実行エラーを調査し、原因を特定して解決策を提案する。「Actions エラー」「ワークフロー失敗」「CI が落ちた」「ビルド失敗」「テスト失敗」「Actions を調べて」「CI のエラーを見て」などで起動。失敗したジョブのログを分析し、具体的な修正方法を提示。 — from…
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until…
Diagnose a Promaker managed site that is failing and try to fix it automatically — all in one flow. Resolves the site, pulls deployments + build logs + runtime logs via the…
Use when diagnosing Apex behavior with debug logs, choosing log levels, or replacing `System.debug` habits with structured production logging and async job monitoring.
Debug HTTP/network/API failures in mParticle Web SDK including fetch failed/fetch error/request failed/API call failed/endpoint not responding/401 unauthorized/403 forbidden/404…
Frontend-backend arasındaki API hatalarını (401, 403, 404, 500, CORS) sistematik olarak teşhis ve çözümler
Build and test this repo with the CMake preset debug-asan (AddressSanitizer). Use when asked how to configure, build, run, or test with ASAN/debug builds in this project.
Assistência em debugging e troubleshooting de aplicações PHP/Laravel incluindo análise de stack traces, logs, erros de banco de dados, problemas de performance, memory leaks, e…
Debug frontend, browser, runtime, build, hydration, routing, network, console, Playwright, visual regression, responsive layout, accessibility, and user interaction issues in…
Use when a stack trace appears, a test fails, code throws unexpectedly, or the user says something is broken.
Configures and builds YARS with debug symbols for debugging with valgrind or gdb
All pods run in namespace crs. Use when pods in the crs namespace are in CrashLoopBackOff, OOMKilled, or restarting, multiple services restart simultaneously (cascade failure), or…
Reproduce and debug CI failures locally using Docker. Use when a CI job fails but tests pass locally, especially for Linux-specific issues (VSCode extension tests with xvfb, Go…
Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior.
Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting…
查询 coffee-ahk 编译架构、bug 定位方法、调试技巧，use when debugging/fixing bugs or need to understand compilation flow
Debug WebSocket connection issues between CLI and FigJam plugin. Use when diagrams aren't syncing or connection fails.
Universal PDCA debugging framework for systematic hypothesis verification. Use when debugging issues that require structured investigation, observing runtime behavior, or…
Debug data storage and persistence issues. Use when troubleshooting lost data, storage problems, or state persistence bugs.
Systematic debugging approach for ANY codebase, ANY language, ANY bug type. Use when facing unexpected behavior, crashes, performance issues, or intermittent problems.
Guide for debugging distributed training issues in AReaL. Use when user encounters hangs, wrong results, OOM, or communication errors.
Debug hanging issues in SGLang distributed inference (TP/PP/DP/EP). Covers identifying hang locations via py-spy/watchdog/cuda coredump, per-rank logging to find state divergence,…
Run fast DNS lookups, compare record types, and inspect resolver behavior when domains, MX records, or service endpoints look wrong.
[Fix & Debug] Systematic debugging with root cause investigation. Use when bugfix workflow reaches debug step.
Systematically debug and fix errors using structured investigation. Use when the user asks to "debug", "fix an error", "troubleshoot", "investigate a bug", or shares an error…
Use when the user wants a comprehensive multi-issue health pass — fix all bugs, resolve broken tests, clear CI failures, fix lint and type errors, restore green builds — not for a…
Investigate complex bugs, intermittent failures, performance degradations, and system-wide issues requiring deep reasoning across multiple components
Diagnose per-cell failures from `folio materialize` — read the §10.6 envelope, locate the bad cell in `provenance.jsonl`, narrow with a positional target + `--ids`, and re-run…
Debug frontend-backend integration issues for any project by analyzing backend logs, identifying incorrect API calls, and fixing both sides.
Automated URL fetch failure handling with strategy exhaustion, memory learning, and human-in-the-loop recovery.
Debug FFmpeg integration and video/audio processing issues. Use when the user encounters FFmpeg errors, audio extraction problems, codec issues, or video processing failures.
Use Firefox DevTools MCP when an agent needs to inspect pages, trace network and console activity, capture screenshots, and automate reproduction steps in Firefox instead of…
Auto-trigger khi gặp error, bug, exception, traceback, "không chạy", "bị lỗi", "sao lại", "why is", "crash", "undefined", "TypeError", "KeyError", "AttributeError", "ImportError",…
Guia de como descrever problemas de visualização de mapas para uma IA, garantindo que o "Agente Debugger" tenha o contexto para corrigir rotas e dependências.
Add contextual logging to the exact call sites a bug passes through, run the repro, collect the logs, then REMOVE the logs.
Debug the Nuxt 3 admin UI using Playwright MCP for visual inspection, console error analysis, and network request tracing.
Debug Tuist-generated project failures across generation, build, and runtime. Use when `tuist generate`, generated Xcode workspaces, or generated app launches fail or beh — from…
Diagnose and fix common Haskell Bazel build errors, especially dependency visibility issues
Systematic debugging strategies, troubleshooting methodologies, and problem-solving techniques for code and system issues.
Help debug code by analyzing error messages, identifying root causes, and providing fix suggestions.
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly. — from engineering/engineering-misc
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly. — from engineering/engineering-misc
The deterministic mechanics of a Smatchet debug investigation — the NDJSON [temp-debug] instrumentation recipe, build + exe-staleness commands, the unified-CLI run reference,…
Hypothesis-driven debugging with ranked hypotheses, git bisect strategy, instrumentation planning, and minimal reproduction design.
Systematically debug issues in PhotoClove by examining code, state, logs, and data flow. Automatically invoked when investigating bugs, errors not working as expected, or tracing…
Debug bugs and errors using intel-first approach with systematic root cause analysis. Use proactively when errors occur, tests fail, or unexpected behavior appears.
Debug the Copilot Knowledge service - investigate sync failures, schema mismatches, and data issues between tenants.
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification.
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification.
Pull DOM, console, network, and CDP telemetry from a live Chromium session when an agent needs to debug a failing browser task.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across…
Capture and analyze thread backtraces with LLDB/GDB to debug hangs, deadlocks, UI freezes, IPC stalls, or high-CPU loops across any language or project.
Language-specific debug logging patterns and best practices. Reference when adding instrumentation for Dart/Flutter, Kotlin/Android, Swift/iOS, or JavaScript/TypeScript…
\"View recent MCP protocol JSON-RPC messages for debugging. 覽近期MCP協議JSON-RPC訊息以除錯。 Use when: view mcp logs, show mcp messages, debug mcp traffic, inspect json-rpc log, tail mcp…
Use when setting up debug logs and trace flags, reading Apex log output and log levels, running queries in the Developer Console, executing anonymous Apex, or using the Apex…
Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb.
Systematic debugging methodology with 4-phase process, root cause tracing, and elite observability standards. No fixes without investigation.
Analyze MCP JSON-RPC traffic to diagnose protocol and tool call issues. 分析 MCP 協定流量，診斷請求/回應異常。 Use when: tool calls fail, debugging connection issues, inspecting request/response…
Generates a developer debug menu with feature flag toggles, environment switching, network log viewer, cache clearing, crash trigger, and diagnostic info export.