bugfix-quick

nguyenthienthanh's avatarfrom nguyenthienthanh

Fast bug fixes with TDD. Lightweight: understand → test → fix → verify.

⭐3stars🔀2forks📁View on GitHub🕐Updated Jan 8, 2026

When & Why to Use This Skill

The Aura Frog Quick Bugfix skill streamlines the software debugging process using a lightweight Test-Driven Development (TDD) workflow. It enables developers to rapidly identify root causes, create failing tests to reproduce issues, implement minimal fixes, and verify solutions to ensure high code quality and prevent regressions in a fraction of the time.

Use Cases

  • Rapidly identifying and fixing application crashes or runtime errors by creating automated reproduction tests.
  • Correcting unexpected behavior in business logic where specific inputs result in incorrect outputs.
  • Fixing UI and frontend issues, such as broken buttons or incorrect validation messages, using targeted event testing.
  • Performing safe, minimal code patches to resolve regression bugs without the overhead of a full architectural refactor.
namebugfix-quick
description"Fast bug fixes with TDD. Lightweight: understand → test → fix → verify."
autoInvoketrue
prioritymedium
allowed-toolsRead, Grep, Glob, Edit, Write, Bash

Aura Frog Quick Bugfix

Priority: MEDIUM - Use for bugs only, not new features


When to Use

USE for: Bug fixes, errors, crashes, things not working

DON'T use for: New features, major refactors, UI changes → use workflow-orchestrator


Quick Fix Process (4 Steps)

1. Understand (5-10 min)

  • Read error description
  • Locate affected code (Grep/Glob)
  • Identify root cause

2. Write Failing Test (10-15 min) - TDD RED

// Test that reproduces the bug
it('should show error when password is empty', () => {
  fireEvent.press(getByTestId('login-button'))
  expect(getByText('Password is required')).toBeTruthy()
})

Approval: User confirms test FAILS

3. Implement Fix (20-45 min) - TDD GREEN

// Minimal fix
if (!password) {
  setError('Password is required')
  return
}

Approval: User confirms test PASSES

4. Verify (5-10 min)

  • Run full test suite
  • Check no regressions
  • Confirm bug fixed

Approval: User confirms fix works


Template

## Bug Fix: [Description]

**Issue:** [What's broken]
**Root Cause:** [Why]
**Test Added:** [Code]
**Fix Applied:** [Code]
**Verification:** ✅ Tests pass, no regressions

3 approval gates (vs 9 in full workflow) = Much faster!

Remember: Keep fixes minimal. If complex, switch to workflow-orchestrator.