debug▌

Systematic workflow for debugging Claude Code hooks.

You are tasked with helping debug issues during manual testing or implementation. This command allows you to investigate problems by examining logs, database state, and git history without editing files. Think of this as a way to bootstrap a debugging session without using the primary window's context.

This skill helps diagnose and fix common AOTInductor issues.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Use this skill when the user needs root-cause analysis from debug logs: governor-limit diagnosis, stack-trace interpretation, slow-query investigation, heap / CPU pressure analysis, or a reproduction-to-fix loop based on log evidence.

You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.

Diagnose and fix failing Power Automate cloud flows through step-by-step error inspection. \n \n Requires a FlowStudio MCP server connection with valid JWT; see the flowstudio-power-automate-mcp skill for setup \n Provides a structured 8-step workflow: locate flow, find failing run, extract top-level error, read flow definition, inspect action outputs, pinpoint root cause, apply fix, and verify \n Supports fast-path diagnosis via FlowStudio for Teams subscriptions using get_store_flow_errors for

Diagnose and resolve Buttercup CRS pod crashes, cascading failures, and service misbehavior on Kubernetes. \n \n Covers 20+ services across fuzzing, analysis, orchestration, and infrastructure layers; includes triage workflow, log analysis, resource pressure diagnosis, and Redis queue inspection \n Provides cascade-failure detection (e.g., Redis down triggering mass restarts), health-check file monitoring, and per-service failure patterns \n Supports OpenTelemetry/Signoz distributed tracing, vol

debug

Ask the user for: