fix-buglisted

# Fix Bug ## Overview This skill provides a structured, observation-driven methodology for investigating and fixing bugs. Rather than jumping to guesses, it enforces a disciplined loop that builds understanding before making changes. **When to use this skill:** - Investigating a bug report or error - Debugging a failing test - Tracing unexpected behavior in production - Any situation where something is broken and the cause is not immediately obvious **Core principle: Never guess a fix without first understanding the root cause.** --- ## Phase 0: Scope Check (when ticket-driven) If the bug is linked to a ticket (Jira / GitHub), delegate to the `scope-check` skill — auto-loaded by description match on the ticket ID — to enumerate the ticket's acceptance criteria into a checklist BEFORE the observation loop begins. The checklist bounds the fix: it tells you what counts as "done" and what's out of scope. Skip if the bug is reported informally without a ticket. ## Observation-Driven Debugging Effective debugging is not about guessing -- it is about systematically narrowing down the problem space through observation and hypothesis testing. Each cycle brings you closer to the root cause, and even failed hypotheses are valuable data. ### The OHAOI Loop ``` OBSERVE ──► HYPOTHESIZE ──► ACT ──► OBSERVE ──► ITERATE ▲ │ └────────────────────────────────────────────────┘ (if hypothesis disproven) ```