메뉴
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | diagnosing-bugs |
| description | Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. |
| disable-model-invocation | true |
Uses scratch working memory for hypothesis tracking.
RULE: glossary + ADRs. Skip phase only with explicit reason. DO NOT hypothesise before deterministic loop.
MUST build fast pass/fail loop. Try order:
git bisect run harness.scripts/hitl-loop.template.sh.Rules:
Initialize session: .scratch/diagnoses/<YYYY-MM-DD>/zoo-diagnosing-bugs-<slug>/
Write <session-dir>/session.md with symptom, repro steps, error signatures.
Generate 3–5 ranked falsifiable hypotheses. Write each to <session-dir>/hypothesis-<N>.md:
If {cause}, then {probe} will {result}Drop vague hypotheses. Show ranked list. User AFK → proceed top hypothesis.
Before each probe, read all <session-dir>/hypothesis-*.md files to maintain context.
[DEBUG-xxxx].After each probe, update the corresponding hypothesis file with:
Continue until root cause is confirmed or all hypotheses are rejected.
OWNER: code-tweaker (requires source-code edits)
Architect MUST switch_mode to code-tweaker before this phase. Tweaker executes:
Tweaker does NOT call attempt_completion here — more phases remain. Continue to Phase 6.
OWNER: code-tweaker (requires source-code edits and git commit)
MUST finish:
[DEBUG-...] logs removed from source./zoo-improve-codebase-architecture.Tweaker MUST switch_mode back to system-architect for Phase 7.
Before broad reads, locate relevant files/symbols with list_files, search_files, or codebase_search.
Prefer targeted read_file ranges or indentation/block reads once the relevant area is known.
Read full files only when structure, ordering, or surrounding context is required for correctness.
Do not re-read unchanged files; use prior findings unless the file changed.
For logs or large outputs, search for the failing marker/error first. Read only surrounding ranges needed to prove or disprove a hypothesis.
OWNER: system-architect (writes to .scratch/)
Read all <session-dir>/hypothesis-*.md files.
Write <session-dir>/root-cause.md:
Write <session-dir>/diagnosis.md with full log (hypotheses, instrumentation results, timeline).
Call attempt_completion with:
<session-dir>/root-cause.md path/zoo-verify then /zoo-code-review then /zoo-commit-and-document)