DebugPro

Plugin debugpro in therealityreport/toolihan. Commands read from the repo's manifest — 1 month ago.

Skills (21)

• debugpro-adjacent-sweep

  Use when an approved fix needs a bounded same-surface adjacent-defect check.

• debugpro-arbitration

  Use when investigated debugging hypotheses must be compared before choosing a fix.

• debugpro-bisect

  Use when a regression needs an evidence-backed first bad change.

• debugpro-browser-runtime-proof

  Use when a browser, localhost, UI, or web runtime failure needs direct runtime evidence before diagnosis or verification.

• debugpro-bug-hunt

  Use when diffs, logs, traces, or stacks need evidence-backed bug finding.

• debugpro-ci-pr-failure

  Use when CI, PR checks, or GitHub Actions jobs fail.

• debugpro-delta

  Use when a failure needs a minimal reproducible input, fixture, config, or project.

• debugpro-flaky

  Use when tests fail by seed, timing, order, or pollution.

• debugpro-frontend-debugging

  Use when frontend rendering, routing, hydration, state, assets, or browser behavior fails.

• debugpro-hypotheses

  Use when intake is complete but the cause remains unclear.

• debugpro-instrumentation

  Use when existing evidence is insufficient and bounded probes are needed to prove cause.

• debugpro-intake

  Use when a debugging request lacks facts needed for safe diagnosis.

• debugpro-macos-debugging

  Use when macOS build, signing, launch, process, logs, or runtime behavior fails.

• debugpro-mcp-runtime-ownership

  Use when MCP tools, servers, configs, caches, or owners drift.

• debugpro-performance

  Use when slowness, resource use, throughput, or latency needs measurement.

• debugpro-production-debugging

  Use when production logs, traces, metrics, deploys, or flags are the main evidence.

• debugpro-root-cause-tracing

  Use when a symptom needs a proven chain from trigger to defective state.

• debugpro-source-runtime-parity

  Use when source files, packaged files, installed runtime files, caches, generated output, or live behavior may be out of sync.

• debugpro-team

  Use when multiple independent debugging hypotheses can be investigated safely in parallel before arbitration and fixes.

• debugpro-verify

  Use when a candidate fix needs verification against the original failing signal before declaring completion.

• debugpro

  Use when failures need evidence-first root-cause routing.

Subagents (2)

• debugpro-capability-router
• debugpro-investigator

  Investigates exactly one assigned debugging hypothesis with read-only evidence gathering and a structured verdict.

Similar plugins