ClaudeSuperPower

Best of / Subagents

Best Debugging Subagents

5 Subagents in the debugging category, ranked by GitHub stars — updated automatically as our nightly sync refreshes stats.

  1. 1

    workflow-debugger

    Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.

    0
  2. 2

    pixeltable-debugger

    Diagnoses and fixes failing or stale Pixeltable pipelines — errored computed columns, no-op recomputes, retrieval problems, rate limits, and deprecated-API misuse. Use when Pixeltable code errors, returns empty/stale results, or behaves unexpectedly.

    0
  3. 3

    honeycomb-investigator

    Use this agent when the user needs an autonomous, multi-step investigation of a production issue using Honeycomb. Examples: <example> Context: User received a PagerDuty alert about high latency user: "Our checkout API is slow, can you investigate using Honeycomb?" assistant: "I'll use the honeycomb-

    0
  4. 4

    error-analyzer

    Analyze multiple PostHog errors in parallel to identify patterns, root causes, and prioritize fixes based on user impact.

    0
  5. 5

    domino-debug

    Specialized agent for debugging Domino issues including app deployment problems, job failures, environment build errors, and connectivity issues. Use PROACTIVELY when troubleshooting errors or unexpected behavior in Domino.

    0

FAQ

How is this ranked?

By GitHub stars by default. Once a subagent has community reviews, its rating is shown alongside the star count on its detail page.

How often is this updated?

Star counts and READMEs refresh automatically every night via our GitHub sync.