Bugs Flow

Use this skill for the bug workflow family: analyze, fix, and optionally review.

When to use

• The ask is a bug report, regression, crash, incident, or Sentry investigation.
• The user has symptoms, logs, traces, QA notes, or a bug doc and wants the issue analyzed or fixed.
• The work should be driven by evidence and a single bug doc rather than by a feature plan.

When not to use

• The user wants a repo-wide audit pass or leave-it-running defect hunt rather than one known bug. Use audit-loop.
• The work is planned feature delivery or architecture planning. Use arch-step, arch-mini-plan, or lilarch.
• The task is open-ended optimization or a broad investigation loop rather than a concrete bug. Use goal-loop or north-star-investigation.

Non-negotiables