bug-hunt

Estrelas0

Forks0

Atualizado30 de março de 2026 às 02:17

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

speson

speson/omo

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	bug-hunt
description	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.
argument-hint	[symptom]
disable-model-invocation	false
allowed-tools	Read, Edit, MultiEdit, Write, Glob, Grep, Bash, Task

Investigate this bug or symptom: $ARGUMENTS

Restate the bug as a failing expectation.
If .claude/state/memory/failures.md exists, check for similar known failure patterns.
Parallel investigation — dispatch simultaneously:
- 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.
Synthesize findings from all three specialists before editing.
If the cause becomes clear, either fix it directly or hand implementation to build-integrator.
If the first fix attempt fails, escalate to oracle immediately — do not retry the same approach.
End with:
- reproduction
- root-cause hypothesis
- fix status
- verification
- remaining uncertainty

Mais deste repositório

mesmo repositório

ship-check

speson/omo

Review the current diff, run the narrowest useful verification, and summarize remaining release risk. Activate when #sc appears anywhere in the user message.

2026-04-010

status

speson/omo

Show unified omo status dashboard — boulder, ralph-loop, tasks, teams, and memory state at a glance. Activate when #ss appears anywhere in the user message.

2026-03-310

docs-sync

speson/omo

Check if README.md and user guide reflect current project state — philosophy, features, agent models, skill list. Fix any drift. Activate when #sync appears anywhere in the user message.

2026-03-310

release

speson/omo

Full release pipeline — commit, push, tag, GitHub release, marketplace version sync. Activate when #rel appears anywhere in the user message.

2026-03-310

diff-review

speson/omo

Multi-perspective code review on the current diff or specified files. Examines correctness, security, performance, maintainability, and scope creep. Activate when #dr appears anywhere in the user message.

2026-03-300

spawn

speson/omo

Dispatch multiple agents in parallel for independent tasks. Use when work splits cleanly into non-overlapping units that can execute simultaneously. Activate when #sp appears anywhere in the user message.

2026-03-300

name	bug-hunt
description	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.
argument-hint	[symptom]
disable-model-invocation	false
allowed-tools	Read, Edit, MultiEdit, Write, Glob, Grep, Bash, Task

Investigate this bug or symptom: $ARGUMENTS

Restate the bug as a failing expectation.
If .claude/state/memory/failures.md exists, check for similar known failure patterns.
Parallel investigation — dispatch simultaneously:
- 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.
Synthesize findings from all three specialists before editing.
If the cause becomes clear, either fix it directly or hand implementation to build-integrator.
If the first fix attempt fails, escalate to oracle immediately — do not retry the same approach.
End with:
- reproduction
- root-cause hypothesis
- fix status
- verification
- remaining uncertainty