@endgame-build/claude-workflows/.claude/commands/eg/fix.md

Claude Code workflow system with commands, agents, and templates for AI-native development

---
description: Quick targeted fixes for specific issues without full workflow
argument-hint: <description of issue>
---

# /eg:fix

You are tasked with providing quick, targeted fixes for specific issues that don't require extensive debugging or architectural consideration. This command is for rapid issue resolution with minimal, focused changes.

Input: `$ARGUMENTS`

## Step 1: Parse Issue Description

The entire argument is the issue description to fix.

## Step 2: Identify Fix Type

Determine the type of fix needed:
- Typo or syntax error
- Configuration issue  
- Small bug fix
- Missing import/dependency
- Incorrect logic
- Style/formatting issue

## Step 3: Locate and Fix

Use grep to find the issue:

```
# Search for relevant files based on issue description
!grep -r "{search-term}" --include="*.js" --include="*.ts" --include="*.py" . | head -20
```

Make the minimal fix directly:
- Fix only what's described
- Don't refactor unrelated code
- Preserve existing style
- Maintain backwards compatibility

Common quick fixes:

### For typos:
Find and replace the typo directly

### For missing imports:
Add the import at the top of the file

### For config issues:
Update the configuration file

### For logic errors:
Fix the specific condition or operation

## Step 4: Validate Fix

Quick validation:
```
# For JavaScript/TypeScript
!if [ -f "package.json" ]; then
  npm run lint 2>/dev/null || echo "No lint script"
fi

# For Python
!if [ -f "requirements.txt" ]; then
  python -m py_compile {fixed-file} 2>/dev/null || echo "Syntax check"
fi
```

## Step 5: Commit if Fixed

If the fix is successful:
```
!git add {fixed-files}
!git commit -m "fix: {issue-description}"
```

## Guidelines

✅ Use `/eg:fix` for:
- Typos and spelling errors
- Missing semicolons or brackets
- Wrong variable names
- Import path corrections
- Simple logic fixes
- Config updates

❌ Don't use `/eg:fix` for:
- Complex bugs (use `/eg:debug`)
- Feature additions (use full workflow)
- Major refactoring (use `/eg:architect`)
- Security vulnerabilities (need careful review)
- Performance optimizations (need analysis)

The fix should take less than 5 minutes. If it requires investigation, use the debug workflow instead.