/overview

Generate a high-level overview of the code changes in the current review session.

Use the Task tool with:

• subagent_type: general-purpose

• description: Generate code review overview

• prompt: | Provide a high-level summary of code changes in the current review session.

  Instructions

  1. Load session context:

     • Check .diff-feedback/comments.txt exists
     • Parse session metadata from header (Base branch, Files count)
     • Extract base branch or determine if reviewing uncommitted changes

  2. Generate diff:

     # If base branch specified in header
     git diff [BASE_BRANCH]...
     
     # If uncommitted changes
     git diff
     

  3. Analyze changes and generate overview focusing on:

     • SIGNIFICANT changes: New features, logic changes, API modifications, architectural decisions
     • SKIP trivial: Import additions, formatting, whitespace, comment-only changes, minor refactoring

  Output Format

  Overview (X files changed):
  
  Significant Changes:
  
  [For each significant file, grouped logically]
  - path/to/file.ts (NEW|MODIFIED|DELETED): [One-line summary]
    • [Key change 1 with rationale if non-obvious]
    • [Key change 2 with rationale if non-obvious]
  
  [If applicable]
  Integration:
  - file1.ts (MODIFIED): [How it connects to main changes]
  - file2.ts (MODIFIED): [Integration point]
  
  [If skipped files]
  Skipped X files with only: [imports, formatting, comments, type exports]
  
  [If notable]
  Architectural Notes:
  - [Why code structured this way / trade-offs / design decisions]
  - [Performance considerations]
  - [Dependencies or patterns introduced]
  

  Example Output

  Overview (8 files changed):
  
  Core Implementation:
  
  - store/theme/slice.ts (NEW): Redux slice for global theme management
    • Three-way theme mode: light/dark/system with OS preference detection
    • Persists user preference to localStorage with 'theme-mode' key
    • Uses RTK createSlice with immer for immutable updates
  
  - components/ThemeToggle.tsx (NEW): UI component for theme switching
    • Three-button toggle with icons for each mode
    • Real-time system preference detection via matchMedia API
    • Accessible with keyboard navigation and ARIA labels
  
  - hooks/useSystemTheme.ts (NEW): Custom hook for OS preference detection
    • Listens to system theme changes with cleanup
    • Returns 'light' | 'dark' based on prefers-color-scheme media query
  
  Integration:
  
  - App.tsx (MODIFIED): Integrated ThemeProvider at app root
    • Wraps entire app to provide theme context
    • Initializes theme from localStorage on mount with fallback to system
  
  - store/index.ts (MODIFIED): Added theme reducer to store configuration
  
  Skipped 3 files with only: type exports, import additions
  
  Architectural Notes:
  - Chose Redux over Context API because theme is accessed by 20+ components
  - System preference detection uses matchMedia for real-time updates (no polling)
  - localStorage persistence prevents flash of wrong theme on page load
  

  Guidelines

  • Focus on WHY, not just WHAT: Explain rationale for non-obvious decisions
  • Skip obvious changes: Don't mention every import or trivial modification
  • Group logically: Related files together (e.g., "Core Implementation", "Integration", "Tests")
  • Be concise: One-line file summaries, bullet points for details
  • Highlight trade-offs: If there's an interesting design decision, explain it
  • Mention impact: If change affects performance, testing, or architecture

  Important

  • Read .diff-feedback/comments.txt to get session context
  • Use git diff to analyze actual changes
  • Do NOT read or analyze the comment file's review feedback (only use header for context)
  • Provide overview of THE CHANGES, not the review comments
  • Skip files with only imports, formatting, or trivial changes
  • Focus on significant logic, architecture, and feature additions