Use to find a bug's first bad commit or smallest failing input — git bisect run, delta debugging.
Find out why something in a running web app does not work, when the console is empty and the code looks correct.
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…
Debugs a red CI job to root cause instead of blind-rerunning — reproduce locally in the SAME image (`act -j `, `gitlab-runner exec`, `circleci local execute`, or `docker run`…
Investigate a specific Claude Code session by session ID — correlate the local transcript (`~/.claude/projects/...jsonl`) with the router's production logs to understand what the…
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.
Diagnose a failing FriendsOfCake CRUD request — config, events, subject, and ORM boundaries.
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.
Composite skill — full debugging workflow from "this is broken" to root cause and fix. Chains systematic-debugging (root-cause hypotheses) → tracer agent (evidence walk) — from…
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.
Debug and fix failing Playwright E2E tests. Use when tests fail, when asked to fix failing tests, or when investigating test failures.
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…
Debug haiku.rag evaluation runs in Logfire. Use when asked to look at Logfire for an eval run, find failing or low-scoring eval cases, compare runs, check citation quality…
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 and fix failures in a built third-party `.ppmplugin` control: crashes, silent no-ops, PCF error outputs, or incorrect behavior.
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…
See why a Go/Ginkgo Biloba spec failed or flaked — the on-failure artifacts (DOM outline + screenshots + poll trajectory of the timed-out read + the visual-regression diagnosis…
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.
Diagnoses and fixes non-deterministic test failures at root cause instead of masking them with retries — classify the flake (test-order/shared-state pollution, async timing/sleep…
Add contextual logging to the exact call sites a bug passes through, run the repro, collect the logs, then REMOVE the logs.
Debug FlyDSL GPU kernels that produce NaN, inf, wrong results, or crash. Covers cache invalidation, tracing pitfalls (runtime conditionals, range vs range_constexpr), loop-carried…
Debug the Nuxt 3 admin UI using Playwright MCP for visual inspection, console error analysis, and network request tracing.
Diagnoses runtime UI bugs live in the browser — console/network errors, hydration mismatches, failed renders, CORS, broken interactions; used when a page misbehaves at runtime.
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…
Parametri URL, hotkey e hook globali dell'harness di debug del voxel city builder. Usala quando devi riprodurre un comportamento a schermo, misurare un budget di frame, leggere un…
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 TresPies-source/CoworkPluginsByDojoGenesis
Systematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly. — from engineering/engineering-misc
Evidence-first debugging for bugs that are hard to reproduce, intermittent, performance-related, or where previous static-analysis fixes have failed.
Diagnoses and resolves failures reported by WorkOS Agentic Registration scanners, `isitagentready.com`, and SSO/Directory Sync validators — including DNS errors, malformed…
Debug why inference.local, direct external inference, or supervisor-only system inference is failing.
Debug haiku.rag ingestion in Logfire. Use when asked to look at Logfire for ingestion, find failed or dead ingestion jobs, investigate retries or circuit-breaker events, trace a…
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.