fix-buglisted

Resolves a single bug from any starting evidence — Dash0 telemetry (span / log / web event / RUM error link), raw stack trace, error message, code pointer (file:line), screen recording, Linear ticket URL, or free-text symptom. Classifies the input, **triages complexity** (Phase 0.5) to pick between a fast lane and a full holistic-analysis lane, runs a pre-flight sweep, locks a failing reproduction (delegating to /tdd, /e2e-testing, or /e2e-testing-mobile by layer), delegates root-cause analysis to holistic-analysis on complex bugs (or runs a lightweight in-skill analysis on simple ones), gates on confidence(analysis), and on >= 92 % hands off **without human confirmation**: simple bugs take the fast lane (/fix-bug → aw-create-plan → aw-executor, no aw-planner) and complex bugs take the standard lane (aw-planner → aw-executor), both with a CEGIS refinement contract. Fast-lane round-3 CEGIS failure falls back to standard-lane via aw-planner. An independent bug-fix-verifier agent grades the PR before undrafting;
mthines/agent-skills · ★ 4 · Testing & QA · score 83

Install: claude install-skill mthines/agent-skills

# Fix Bug Take a bug — described in any form the user has at hand — and either ship a verified draft PR with the fix or hand back a clear, evidence-backed proposal. This skill is a **thin orchestrator**: heavy reasoning lives in `holistic-analysis`, gating in `confidence`, test authoring in `/tdd` / `/e2e-testing` / `/e2e-testing-mobile`, plan authoring in `aw-planner` (standard-lane) or `aw-create-plan` (fast-lane), implementation in `aw-executor`, and independent grading in `bug-fix-verifier`. This skill owns input classification, **complexity triage**, evidence assembly, the user-facing decision at the confidence boundary, **lane selection**, and a durable bug-notes ledger that survives compaction. > **Source of truth.** This `SKILL.md` is a thin index. Detailed procedures live in `rules/*.md`, > literal artefacts in `templates/*.md`, and external references in `references/*.md`. Load only > what the current phase asks for. ## Architecture ```text Phase 0: Intake → classify input + infer bugClass + detect mode flags Phase 0.5: Complexity Triage → simple | complex (signals + decision rule) Phase 1: Evidence Resolution → per-input resolution + pre-flight sweep (may upgrade triage) Phase 2: Source Mapping + Repro Lock → Evidence Record + failing repro (via /tdd or /e2e-testing*) Phase 3: Analysis → Skill("holistic-analysis", "fix") [complex] OR lightweight in-skill analysis