APAW/.kilo/commands/hotfix.md

description, mode, model, color, permission

description	mode	model	color	permission
Quick bug fix workflow for urgent production issues	hotfix	openrouter/minimax/minimax-m2.5:free	#DC2626	read edit write bash glob grep task allow allow allow allow allow allow * deny

Hotfix Command

Rapid response workflow for urgent production bug fixes with minimal, targeted changes.

Workflow

Step 1: Bug Analysis

Agent: @TheFixer

• Collect bug report information:
  • Error messages
  • Stack traces
  • User-reported symptoms
  • Reproduction steps
• Identify impact:
  • Severity: Critical / High / Medium / Low
  • Affected users: Count and segments
  • System components affected
• Determine urgency:
  • Production down: Immediate
  • Data loss risk: Very High
  • User-facing bug: High
  • Internal tool: Medium

## Bug Report

### Symptom
[What is happening]

### Expected
[What should happen]

### Impact
- Severity: [Level]
- Affected: [Users/Components]
- Urgency: [Level]

### Reproduction
1. [Step 1]
2. [Step 2]
3. [Step 3]

Step 2: Locate Bug

Agent: @TheFixer

• Search for error messages: grep -r "error message" src/
• Find related code: grep "function_name" src/
• Trace stack to source
• Identify root cause:
  • Logic error
  • Data issue
  • Integration failure
  • Environment difference
• Document findings:

  ## Root Cause Analysis
  
  ### Location
  - File: [path]
  - Line: [number]
  - Function: [name]
  
  ### Cause
  [Technical explanation]
  
  ### Trigger
  [What conditions cause the bug]
  

Step 3: Minimal Fix

Agent: @TheFixer

• Principle: Smallest change that fixes the issue
• Do NOT refactor or improve surrounding code
• Do NOT add new features
• Fix must be:
  • Targeted to specific bug
  • Low risk
  • Easy to review
  • Reversible if needed
• Create fix with:
  • Clear before/after behavior
  • Focused change scope

## Fix Proposal

### Change
- File: [path]
- Lines: [range]
- Type: [Logic fix / Condition update / Error handling]

### Before
[code snippet]

### After
[code snippet]

### Reasoning
[Why this fix]

Step 4: Test Fix

Agent: @SDETEngineer

• Create reproduction test:

  it('should [expected behavior] when [condition]', () => {
    // This test reproduces the bug
    // It should FAIL before fix, PASS after fix
  });
  

• Verify test fails without fix
• Apply fix
• Verify test passes with fix
• Run existing tests to check for regressions
• Document test:

  ## Test Verification
  
  ### Reproduction Test
  - File: [test file]
  - Test: [test name]
  - Fails without fix: ✓
  - Passes with fix: ✓
  
  ### Regression Tests
  - All tests pass: ✓
  - Failed tests: [List or None]
  

Step 5: Quick Review

Agent: @CodeSkeptic

• Focus on:
  • Does fix address root cause?
  • Are there obvious side effects?
  • Is change minimal?
• Skip for critical production down:
  • If production is DOWN, proceed to deploy
  • Schedule full review post-deploy
• Review checklist:

  ## Hotfix Review
  
  ### Minimal Change
  - Changes scope: [Lines changed]
  - No unrelated changes: ✓/✗
  
  ### Correctness
  - Addresses root cause: ✓/✗
  - No side effects: ✓/✗
  
  ### Tests
  - Has reproduction test: ✓/✗
  - No regressions: ✓/✗
  
  ### Verdict
  - APPROVE / NEEDS_WORK
  

Step 6: Prepare for Merge

Agent: @ReleaseManager

• Create hotfix branch from main
• Apply changes
• Update CHANGELOG.md:

  ## [Unreleased]
  
  ### Fixed
  - [Bug description] fixing #[issue]
  

• Commit with clear message:

  fix: [brief description]
  
  - Root cause: [explanation]
  - Fix: [what changed]
  - Fixes #[issue]
  

• Only merge if user explicitly requests
• Post-merge actions:
  • Monitor for issues
  • Schedule retrospective
  • Update documentation if needed

Hotfix Branch Strategy

main ───●───●───●───●
            \       
hotfix/xxx   ●───●
            /
main ───────●───●───● (merge back)

1. Branch from main
2. Apply minimal fix
3. Test thoroughly
4. Merge to main
5. Tag release

Quality Gates for Hotfix

Gate	Requirement
Root cause identified	Must
Minimal change scope	Must
Reproduction test	Must
No regressions	Must
Reviewed	Unless production down

Post-Hotfix Actions

1. Monitor: Watch logs and metrics for 24-48 hours
2. Document: Update runbooks if applicable
3. Retrospective: Schedule bug postmortem
4. Prevention: Add checks to prevent recurrence:
   • Additional tests
   • Monitoring alerts
   • Validation rules

Rollback Plan

If hotfix causes issues:

1. Revert commit immediately
2. Restore previous version
3. Investigate regression
4. Create new hotfix if needed

# Rollback command
git revert <hotfix-commit>
git push origin main

Time Targets

Severity	Target Resolution
Critical (prod down)	30 minutes
High (user impact)	2 hours
Medium (internal)	4 hours
Low (minor)	Next sprint

Escalation

If fix is not straightforward:

• Complex fix needed → Upgrade to /feature workflow
• Requires redesign → Escalate to architect
• Data migration needed → Coordinate with DBA