---
description: Quick bug fixes without full task structure
argument-hint: "[issue description]"
agent: build
---

# Fast Fix: $ARGUMENTS

## For Simple One-Liner Fixes (No Task Needed)

**Proceed directly if:**

- Single file, single function
- Clear root cause identified
- Fix is obvious (2-3 line change)

**Example:**

```typescript
// Fix: Handle null case in parser (issue #45)
if (!input) {
  return null; // Added this line
}
```

Then: `git commit -m "fix: $ARGUMENTS"`

## For Complex Bug Fixes (Task File Recommended)

**Create task if:**

- Root cause unclear
- Multiple files affected
- Potential regressions possible
- Fix requires testing strategy

---

## Phase 1: Quick Analysis (No Task)

### Analyze Issue

```
STEPS:
1. Understand issue: $ARGUMENTS
2. Identify root cause using available tools
3. Propose minimal fix
4. Verify fix doesn't break existing code
5. Add clear comments explaining the fix
```

**Analysis Tools:**

- Code search: Use finder to locate related code
- Testing: Run existing tests to validate
- Documentation: Check API docs for expected behavior

## Phase 2: Fix Implementation

### Before Modifying

Ask yourself:

- Is root cause clear?
- Will this fix resolve the issue completely?
- Are there edge cases to consider?
- Will existing tests still pass?

### Implement

- Make minimal change only
- Add comments explaining why
- Test locally if possible

### After Modifying

```bash
git commit -m "fix: clear description of what was broken and why"
```

---

## For Task-Based Complex Fixes

### Create Bug Fix Task (Optional)

Use `/task-with-spec "Fix: $ARGUMENTS"` if:

- Complex logic involved
- Need to track decisions
- Want documented analysis

Then follow standard task workflow.

---

**ANTI-HALLUCINATION: Simple fixes proceed directly; complex bugs get task tracking**
