review-changeslisted

# Review Git Changes ## Instructions Perform thorough code review of current working copy changes, optionally compare to plan, and identify engineering issues. ### Phase 1: Discover Changes & Context #### Step 1: Get Current Changes ```bash # See changed files git status # See detailed diff git diff # See staged changes separately git diff --cached # See both staged and unstaged git diff HEAD ``` #### Step 2: Identify Related Plan (if exists) Search for related plan file: - Check `.plans/` directory for relevant plan - Look for plan mentioned in branch name - Ask user if unsure which plan applies - If no plan exists, review against general best practices If plan exists: - Read the entire plan - Understand intended design and architecture - Note specific requirements and constraints #### Step 3: Categorize Changed Files Group files by type: - **New files**: Created from scratch - **Modified files**: Existing files changed - **Deleted files**: Removed files - **Renamed/moved files**: Organizational changes Create todo list with one item per changed file to review. ### Phase 2: Systematic File Review For EACH changed file in the todo list: #### Step 1: Read Current State - Read the entire file in its current state - Understand what it does - Note its responsibilities #### Step 2: Analyze the Changes Read git diff to see exactly what changed: - What was added? - What was removed? - What was modified? #### Step 3: Assess Against Plan (if applicable) If plan exi