← ClaudeAtlas

bug-fixlisted

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`).
ramboz/jig · ★ 6 · Testing & QA · score 74
Install: claude install-skill ramboz/jig
> **Working posture ([ADR-0056](../../docs/decisions/adr-0056-adversarial-register-quarantine.md)).** > Adversarial review is a *named, bounded operation.* This workflow invokes > review passes (bug-review / craft), whose skeptical register belongs *inside* > those isolated reviewer subagents. Outside a review, default to collaborative > and solution-forward; don't carry the adversarial stance into ordinary > conversation. > Spec 058 / [ADR-0016](../../docs/decisions/adr-0016-bug-fix-lifecycle.md) > built this workflow. The deterministic state mutations and teeth gates live > in `bug.py`; this SKILL.md drives the judgment layer. It is a **peer of > `spec-workflow`** — a first-class jig workflow that owns its orchestration, > not a deferring baseline. ## What this skill does - Routes a reported bug to the **proportional** path: `triage` bows out of trivial work, reserving the record + gates for standard/gnarly tiers. - Drives the bug lifecycle state transitions via `bug.py transition`, which enforces the teeth gates (diagnose-before-fix; red→green). - Coordinates reviewer-subagent passes (bug-review, craft, conditional security) at `→ REVIEWED`, validated by the ADR-0014 evidence gate. - Rechecks fresh main after `ROOT_CAUSED` and before `FIXING` so a stale parallel session does not re-fix a bug already solved on trunk. - Provides the first-class escalation seam (`bug.py escalate`) for when a bug turns out to be a missing or under-specified behaviour. - Imports th