fix-bug

Solid

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 the isolated rca-investigator agent (holistic-analysis + confidence) 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-

AI & Automation 8 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# 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` (dispatched isolated via the `rca-investigator` agent on the complex lane), 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 → Task(rca-investigator) — isolated holis...

Details

Author: mthines
Repository: mthines/agent-skills
Created: 3 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

bug-fix

Drive the teeth-gated lifecycle for reported defects: diagnose root cause, prove it, and prevent regression through REPORTED → DIAGNOSING → ROOT_CAUSED → FIXING → REVIEWED → DONE, with VERIFIED, ESCALATED, and RESOLVED_ON_MAIN paths where needed. Auto-fires on fix this bug, debug this, root-cause this, this regressed, this broke again, why is this failing, diagnose before fixing, or investigate this failure. Two modes: `diagnose` stops at ROOT_CAUSED; `diagnose_and_fix` runs through DONE. Uses a durable bug record, multiple hypotheses, a fresh-main recheck, and a witnessed red→green test. Do not use for spec-shaped work (use `spec-workflow`) — including a pure visual design-fidelity gap against an agreed mockup, which is spec-shaped, not a bug (see "Design-fidelity triage" below) — or trivial one-liners (use `tdd-loop`).

5 Updated yesterday

ramboz

AI & Automation Listed

bugfix

Use when a bug is reported, something is broken, an error or crash needs fixing, a wrong output appears, or a regression shows up — guides Grimoire's Reproduce → Root-Cause → failing-test-FIRST → Fix → Verify discipline and will not let the fix begin until a failing regression test is recorded. Use also when the user says "bugfix", "/bugfix", "fix this bug", or "something is broken".

7 Updated yesterday

grimoire-rs

AI & Automation Listed

bug-fix

Use when investigating or fixing a bug, error, crash, regression, or unexpected behavior. Enforces reproduce-first, evidence-based root cause analysis, and a regression test before the fix.

1 Updated yesterday

suleymanbyzt