Claude-Code-Workflow/.claude/skills/ccw/phases/actions/bugfix.md

Action: Bugfix Workflow

缺陷修复工作流：智能诊断 + 影响评估 + 修复

Pattern

lite-fix [--hotfix]

Trigger Conditions

• Keywords: "fix", "bug", "error", "crash", "broken", "fail", "修复", "报错"
• Problem symptoms described
• Error messages present

Execution Flow

Standard Mode

sequenceDiagram
    participant U as User
    participant O as CCW Orchestrator
    participant LF as lite-fix
    participant CLI as CLI Tools
    
    U->>O: Bug description
    O->>O: Classify: bugfix (standard)
    O->>LF: /workflow:lite-fix "bug"
    
    Note over LF: Phase 1: Diagnosis
    LF->>CLI: Root cause analysis (Gemini)
    CLI-->>LF: diagnosis.json
    
    Note over LF: Phase 2: Impact Assessment
    LF->>LF: Risk scoring (0-10)
    LF->>LF: Severity classification
    LF-->>U: Impact report
    
    Note over LF: Phase 3: Fix Strategy
    LF->>LF: Generate fix options
    LF-->>U: Present strategies
    U->>LF: Select strategy
    
    Note over LF: Phase 4: Verification Plan
    LF->>LF: Generate test plan
    LF-->>U: Verification approach
    
    Note over LF: Phase 5: Confirmation
    LF->>U: Execution method?
    U->>LF: Confirm
    
    Note over LF: Phase 6: Execute
    LF->>CLI: Execute fix (Agent/Codex)
    CLI-->>LF: Results
    LF-->>U: Fix complete

Hotfix Mode

sequenceDiagram
    participant U as User
    participant O as CCW Orchestrator
    participant LF as lite-fix
    participant CLI as CLI Tools
    
    U->>O: Urgent bug + "hotfix"
    O->>O: Classify: bugfix (hotfix)
    O->>LF: /workflow:lite-fix --hotfix "bug"
    
    Note over LF: Minimal Diagnosis
    LF->>CLI: Quick root cause
    CLI-->>LF: Known issue?
    
    Note over LF: Surgical Fix
    LF->>LF: Single optimal fix
    LF-->>U: Quick confirmation
    U->>LF: Proceed
    
    Note over LF: Smoke Test
    LF->>CLI: Minimal verification
    CLI-->>LF: Pass/Fail
    
    Note over LF: Follow-up Generation
    LF->>LF: Generate follow-up tasks
    LF-->>U: Fix deployed + follow-ups created

When to Use

Standard Mode (/workflow:lite-fix)

✅ Use for:

• 已知症状的 Bug
• 本地化修复（1-5 文件）
• 非紧急问题
• 需要完整诊断

Hotfix Mode (/workflow:lite-fix --hotfix)

✅ Use for:

• 生产事故
• 紧急修复
• 明确的单点故障
• 时间敏感

❌ Don't use (for either mode):

• 需要架构变更 → /workflow:plan --mode bugfix
• 多个相关问题 → /issue:plan

Severity Classification

Score	Severity	Response	Verification
8-10	Critical	Immediate	Smoke test only
6-7.9	High	Fast track	Integration tests
4-5.9	Medium	Normal	Full test suite
0-3.9	Low	Scheduled	Comprehensive

Configuration

const bugfixConfig = {
  standard: {
    diagnosis: {
      tool: 'gemini',
      depth: 'comprehensive',
      timeout: 300000  // 5 min
    },
    impact: {
      riskThreshold: 6.0,  // High risk threshold
      autoEscalate: true
    },
    verification: {
      levels: ['smoke', 'integration', 'full'],
      autoSelect: true  // Based on severity
    }
  },
  
  hotfix: {
    diagnosis: {
      tool: 'gemini',
      depth: 'minimal',
      timeout: 60000  // 1 min
    },
    fix: {
      strategy: 'single',  // Single optimal fix
      surgical: true
    },
    followup: {
      generate: true,
      types: ['comprehensive-fix', 'post-mortem']
    }
  }
}

Example Invocations

# Standard bug fix
ccw "用户头像上传失败，返回 413 错误"
→ lite-fix
→ Diagnosis: File size limit in nginx
→ Impact: 6.5 (High)
→ Fix: Update nginx config + add client validation
→ Verify: Integration test

# Production hotfix
ccw "紧急：支付网关返回 5xx 错误，影响所有用户"
→ lite-fix --hotfix
→ Quick diagnosis: API key expired
→ Surgical fix: Rotate key
→ Smoke test: Payment flow
→ Follow-ups: Key rotation automation, monitoring alert

# Unknown root cause
ccw "购物车随机丢失商品，原因不明"
→ lite-fix
→ Deep diagnosis (auto)
→ Root cause: Race condition in concurrent updates
→ Fix: Add optimistic locking
→ Verify: Concurrent test suite

Output Artifacts

.workflow/.lite-fix/{bug-slug}-{timestamp}/
├── diagnosis.json       # Root cause analysis
├── impact.json          # Risk assessment
├── fix-plan.json        # Fix strategy
├── task.json            # Enhanced task for execution
└── followup.json        # Follow-up tasks (hotfix only)

Follow-up Tasks (Hotfix Mode)

{
  "followups": [
    {
      "id": "FOLLOWUP-001",
      "type": "comprehensive-fix",
      "title": "Complete fix for payment gateway issue",
      "due": "3 days",
      "description": "Implement full solution with proper error handling"
    },
    {
      "id": "FOLLOWUP-002",
      "type": "post-mortem",
      "title": "Post-mortem analysis",
      "due": "1 week",
      "description": "Document incident and prevention measures"
    }
  ]
}