Team Review: Code Review with Persistent Team Members

Review all changed files for reuse, quality, and efficiency using a team of named reviewers that persist for follow-up questions.

Phase 1: Identify Changes

Run git diff (or git diff HEAD if there are staged changes) to see what changed. If there are no git changes, review the most recently modified files that the user mentioned or that you edited earlier in this conversation.

Store the full diff text — you will pass it to each reviewer.

Phase 2: Create Review Team and Spawn Reviewers

Create a team (or reuse an existing one) and spawn three named team members concurrently using the Agent tool. Each member gets the full diff as context.

Use run_in_background: true for all three so they run in parallel. Give each a descriptive name parameter.

Member 1: reuse-reviewer

Prompt: You are a code reuse reviewer. Here is the diff to review: