quick-fix

📋 TEMPLATE: This command is a template. See "Customization Guide" below to adapt for your infrastructure.

Execute streamlined workflow for small, urgent bug fixes that need fast turnaround.

When to Use

Quick fixes are appropriate for:

• ✅ Critical bugs blocking team
• ✅ Small, isolated changes (< 50 lines)
• ✅ No architecture changes
• ✅ Existing test coverage adequate

NOT for:

• ❌ New features
• ❌ Large refactors
• ❌ Breaking changes
• ❌ Dependency upgrades

Streamlined Workflow

1. Setup (Fast)

If WOR number provided ($1):

• Fetch ticket: mcp__linear-mcp__get_issue $1
• Verify it's a bug fix
• Create branch: git checkout -b ASP-$1-fix-{description}

If no argument:

• Ask for WOR number
• Proceed with setup

2. Make Fix

Guide user:

• Identify the bug location
• Make minimal, focused change
• Test locally
• Commit with clear description

git add .
git commit -m "fix(scope): resolve {issue} [ASP-XXX]"

3. Fast Validation

Run essential checks only:

npm run build    # TypeScript
npm test         # Jest tests

Skip if time-critical:

• Integration tests
• Full build verification

4. Quick PR

git fetch origin && git rebase origin/dev
git push --force-with-lease origin {branch}

Create PR with minimal template:

## 🐛 Quick Fix

**Linear**: [ASP-XXX](link)
**Type**: Bug fix
**Urgency**: High

### Issue

Brief description of bug

### Fix

What was changed (1-2 sentences)

### Testing

- [ ] Manually tested
- [ ] Unit tests pass
- [ ] No regressions expected

### Merge Fast?

- [ ] Yes, this is blocking team
- [ ] No, normal review process

5. Notify Team

If urgent:

• Tag reviewers in PR
• Comment in Linear ticket
• Notify in Slack (if configured)

Success Criteria

• ✅ Fix applied in < 30 minutes
• ✅ Essential validations pass
• ✅ PR created with clear context
• ✅ Team notified if urgent

Safety Checks

Even in quick fixes:

• ✅ Commit message follows SAFe format
• ✅ Branch naming correct
• ✅ Linear ticket referenced
• ✅ TypeScript & ESLint pass