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.
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…
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.
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.
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.
Debug why a Hyperlane message is not being processed. Use when given a message ID or explorer URL to investigate delivery failures, gas estimation errors, validator issues, or…
Systematic debugging and problem-solving methodology. Activate when encountering unexpected errors, service failures, regression bugs, deployment issues, or when a fix attempt has…
Map a minified error stack trace from a production Dyad build back to original source locations using source maps.
Autonomous debugging workflow mirroring Cursor IDE's debug mode. Triggers on "debug mode", "help me debug", error messages, stack traces, or debugging loops.
Debug Sui Move compile errors, runtime aborts, or capability leaks. Use when the user has a Move error, abort code, failed PTB, or compiler issue.
Diagnose why an agent harness misbehaved by reading the local flight-recorder ledger (.vigiles/runs.jsonl) — which skills fired or got hijacked, which hooks blocked or wrongly…
Debug a Nativewind v5 setup issue. Walks through common configuration problems with metro, babel, postcss, and dependencies.
Multi-source debug — Docker logs, Redis inspection, SQL diagnostics, git blame, execution traces
Enable verbose / trace-level logging across the iEvo pipeline. Use when the user wants to debug an init, evolution, or security-audit session — captures full prompts, full…
SSH into openclaw and figure out what's going on. Use when: (1) user says "debug openclaw", "openclaw is broken", "something's wrong with openclaw", (2) agents aren't responding,…
Systematic debugging methodology, language-specific debuggers, and common scenario playbooks. Use for: debug, debugging, bug, crash, hang, memory leak, race condition, deadlock,…
Debugging optimized builds skill for diagnosing issues in release code. Use when debugging RelWithDebInfo builds, using -Og for debuggable optimization, working with split-DWARF,…
Snapshot a channelhub session's tmux pane PLUS its recent autopilot errors and registry state in one structured dump.
Automated PDF failure analysis and fixture generation. Takes failed PDF URLs, identifies breaking patterns, and generates minimal fixtures via fixture-tricky for regression…
Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation.
Trace-first debugging for a live or recent Flintmere production incident. Use when users report an outage, errors spike in logs, a scan fails at scale, or a payment webhook is…
Debug production issues on Vercel using logs, database inspection, and proper deployment waiting
Structured debugging output for bugs, errors, stack traces, or unexpected behavior. Enforces the format Symptom → Root cause → Fix → Why this approach.
Debug React issues systematically. Use when encountering component errors like "Cannot read property of undefined", infinite re-render loops with "Too many re-renders", stale…
Debug React Native issues systematically. Use when encountering native module errors like "Native module cannot be null", Metro bundler issues including port conflicts and cache…