“Debugging”

Use when the user wants to review or inspect past query executions in Honeydew — what ran, from which client (BI tools, SQL interface, MCP, deep analysis)…

Applies a modified Fagan Inspection methodology to resolve persistent bugs and complex issues.

Find the cause of a defect before proposing a fix - read errors, reproduce, check recent changes, gather evidence from this repo's code map and verification…

Use when diagnosing a failure, flaky behavior, or unexpected output before attempting a fix.

Debug errors, test failures, incorrect output, browser failures, intermittent bugs, and performance regressions through a tight red/green diagnosis loop.

Root-cause a failure with an evidence-first loop (reproduce, one hypothesis, minimal probe, smallest fix, re-run).

Advanced debugging assistance and error analysis.

Diagnose Fireworks training and deployment issues, including stuck or failed jobs, error messages, poor quality, checkpoint and resume problems, LoRA adapter…

Resolve failures with an evidence-first loop and a verified fix.

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before…

Diagnose and fix problems in the current Kooboo site through an evidence-first workflow using Preview diagnostics, Network, Browser Control, source…

Diagnose and fix problems in the current Kooboo site through an evidence-first workflow using Preview diagnostics, Network, Browser Control, source…

Debug failed Konflux e2e test runs by downloading logs and artifacts from GitHub Actions or OpenShift CI (Prow), analyzing test failures, and suggesting fixes.

Diagnose PostHog Surveys configuration and responses across all five SDKs (web/posthog-js, iOS, Android, Flutter, React Native).

Systematic debugging methodology, language-specific debuggers, and common scenario playbooks.

Use when debugging and needing falsifiable hypotheses, alternative explanations, or stronger root-cause discipline

Debugging from evidence: read the failure, form one hypothesis, test it.

Troubleshoot and debug issues.

Find the root cause before proposing any fix.

Debug broken runtime/environments by checking logs and observability first, then code.

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

Develop firmware on the real board behind a debug probe: flash, reset, UART and CAN, policy-gated.

Debug and fix failing tests or errors

Debug issues through structured investigation, failing test creation, and targeted fixes.