implement-fix

Context

• Branch: !git branch --show-current
• Date: !date +%Y-%m-%d

Instructions

Step 1: Load Fixes File

Find and read the review fixes file:

1. First, check for REVIEW_FIXES.md in the project root
2. If not found, use Grep to search for files containing type: review-fixes in *.md files
3. If no fixes file exists, inform user to run /code-review:fixes-plan first

Step 2: Determine Scope

Based on $ARGUMENTS:

• Number (e.g., "3") → Implement specific issue #3
• "all" → Implement all pending issues
• Empty → Show pending issues and ask which to implement

Step 3: Analyze Each Issue

For each issue to implement:

1. Read the issue details:

   • File path and line numbers
   • Problem description
   • Suggested solution

2. Read the current code:

   • Understand the context
   • Check if issue still exists (may have been fixed already)

3. Classify the fix:

   Simple fixes (implement directly):

   • Typos, formatting
   • Missing imports
   • Obvious null checks
   • Documentation updates

   Decision-required fixes (ASK FIRST):

   • Multiple valid approaches exist
   • Architectural implications
   • Adding dependencies
   • Performance trade-offs
   • Breaking changes
   • Security-related changes

Step 4: For Decision-Required Fixes

STOP and ask before implementing:

This fix requires a decision:

**Issue #X:** [Brief description]

**Options:**
1. [Approach A]
   - Pros: ...
   - Cons: ...

2. [Approach B]
   - Pros: ...
   - Cons: ...

**Recommendation:** [Your suggestion] because [reasoning]

Which approach do you prefer?

Wait for user response before implementing.

Step 5: Implement the Fix

1. Make the code change:
   • Use Edit tool for modifications
   • Follow existing code patterns
   • Keep changes minimal and focused