bugfix-quick

Solid

Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.

AI & Automation 24 stars 3 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Quick Bugfix For bugs only. Features/refactors → run-orchestrator. --- ## Core Principle **NO FIXES WITHOUT ROOT CAUSE.** Fix at SOURCE, not symptom. ## Process (4 Steps) | Step | Name | Agent | Statusline | |---|---|---|---| | S1 | Investigate | `lead` (inline) — uses Read/Grep/Bash to reproduce | `bugfix S1` | | S2 | Test RED | `tester` — writes failing test | `bugfix S2` | | S3 | Fix GREEN | `architect` / `frontend` / `mobile` (per artifact, via `agent-detector`) | `bugfix S3` | | S4 | Verify | `tester` — runs full suite | `bugfix S4` | **Announce per step.** When transitioning, surface to the user: `─── Step S{N} · {Name} ─── Dispatching {agent}…`. Also update `run-state.json#current_step` (one of: `investigate`, `test-red`, `fix-green`, `verify`) and `#active_agent` so the statusline reflects reality. ### 1. Investigate - Read error + stack trace - Reproduce the bug - `git log` / `git diff` for recent changes - Trace backward: where did bad data originate? - **Context economy** (`rules/core/context-economy.md`) — Grep for the failing symbol first, then Read with `offset`+`limit` on the matched lines only. Don't read the full file unless the bug spans it. ### 2. Write Failing...

Details

Author: nguyenthienthanh
Repository: nguyenthienthanh/aura-frog
Created: 10 months ago
Last Updated: yesterday
Language: JavaScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

awesome-bug-fix

Fixes a bug by building a runnable reproduction and finding the root cause before any fix. Use for errors, crashes, failing tests or builds, flaky behavior, or repeated failed fixes.

10 Updated yesterday

khasky

Code & Development Listed

bugfix

Use whenever a bug is reported and a fix is asked for, however small the fix looks, even a one-line change: the regression test comes before the edit, so do not patch the code directly on a bug report. Investigate root cause, write a failing regression test (RED), implement the minimum fix, confirm the test passes (GREEN), then commit test and fix together. Fires on "fix this bug", "this is broken", "it's not working", "there's a regression", "resolve this issue", "X returns Y instead of Z, fix it", or a reference to a bug report. Not for: planning multi-step work (/aidex:plan); executing a written plan phase-by-phase (/aidex:plan-exec); recording why a fix was chosen as an ADR (/aidex:decision); pure refactors with no bug.

2 Updated 4 days ago

yacb2

DevOps & Infrastructure Listed

fix

Fix issues end-to-end across data pipelines (Airflow/dbt), app stack (backend/frontend), and infra (CI/CD, Terraform, K8s). Scout → diagnose → apply at root cause → verify with fresh evidence → add regression guard. Use for failing DAGs, dbt test failures, 5xx, UI regressions, GH Actions failures, terraform drift, CrashLoopBackOff, lint/type errors. Stops after 3 failed attempts to question architecture.

8 Updated 2 days ago

vanducng