Stats
Actions
Tags
From omo
Triage a failure by capturing symptoms, narrowing reproduction, isolating likely files, and choosing the smallest useful verification loop. Activate when #bh appears anywhere in the user message.
How this skill is triggered — by the user, by Claude, or both
Slash command
/omo:bug-huntThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate this bug or symptom: $ARGUMENTS
Investigate this bug or symptom: $ARGUMENTS
.claude/state/memory/failures.md exists, check for similar known failure patterns.bug-hunter to narrow likely causes and reproduction paths.deepsearch to trace all usages of the suspected code path.test-commander for the smallest verification loop that can validate the hypothesis.build-integrator.oracle immediately — do not retry the same approach.npx claudepluginhub speson/omo --plugin omoIsolates root cause of bugs through systematic hypothesis-and-test cycles. Active before any fix is written — use when behavior diverges from specification.
Applies Zeller's scientific method to debug software: reproduce, hypothesize, binary-search isolate, fix root cause, add regression test. Triggers on bug, error, crash, stack trace.
Enforces structured root-cause analysis for bugs, test failures, errors, warnings, and performance regressions before proposing fixes. Uses phases: known issues, investigation, pattern comparison, hypothesis testing.