Bug Fixing Workflow

Entry Interaction

/fix

bugs/pending.csv

Interaction Process

1. Read

   bugs/pending.csv

2. AskUserQuestion lists pending bugs for the user to select (by ID)
3. Update the status of the selected bug to

   in_progress

   (update the entire row, rewrite the file without blank lines)
4. Automatically execute the 8-stage process

CSV Structure

pending.csv (Written by QA, Read by RD)

id,title,description,severity,reporter,created_at,status,related_dev

• related_dev: Directory name of the associated development task (e.g., User Points-20260120143052)

archived.csv (Written by RD, Accepted by QA)

id,title,description,severity,reporter,created_at,root_cause,fix_plan,affected_scope,fix_report,fixed_at,fixed_by

8-Stage Process

Stage 1: Bug Analysis

• Parse the bug description
• Reproduce the problem path in combination with the current project code
• Output: Problem phenomenon description

Stage 2: Root Cause Identification

• Locate the specific file, function, and line number
• Analyze code logic to find the root cause
• Output: Root cause analysis report

Stage 3: Root Cause Review

• AskUserQuestion to confirm the root cause judgment
• Proceed after user confirmation

Stage 4: Repair Solution

• Design a repair solution based on the existing architecture
• Evaluate repair complexity
• Output: Repair solution overview

Stage 5: Impact Scope

• List affected modules/interfaces/components
• Evaluate regression risks
• Output: Impact scope list

Stage 6: Execute Repair

• ⚠️ Re-read the CLAUDE.md specification before execution
• Modify in batches (≤20 lines)
• Mark repair progress in real-time

Stage 7: Retest Verification

• Automated verification with Playwright or manual verification
• Confirm the problem has been fixed
• Output: Verification result

Stage 8: Archiving and Traceability

• ⚠️ Re-read the CLAUDE.md specification before execution
• Delete the row from pending.csv (rewrite the file without blank lines)
• Append the entire row of data + repair fields to archived.csv

CSV Operation Specifications

• After deleting a row, the entire file must be rewritten to ensure no blank lines
• Operate on entire rows; it is forbidden to operate a single column separately to avoid misalignment
• When moving to archived, copy all fields of the original row completely and then append new fields

Collaboration with QA

• QA submits bugs to pending.csv (generates a unique ID: BUG-yyyymmdd-xxx)
• RD selects an ID via /fix to execute the repair
• QA queries archived.csv to accept the repair results