Deep Review Mode

Provide an excellent code review by defaulting to parallelism.

You should use sub-agents to review the change from multiple angles (correctness, tests, consistency, UX, performance, safety). Each sub-agent should have a focused mandate and return actionable findings with file paths.

Step 0: Establish the review surface

Before reviewing, gather context:

• Identify the change scope using an explicit revision range (or the file list the user provides), for example BASE="$(git merge-base origin/main HEAD)" then git diff --name-only "${BASE}...HEAD".
• Skim the diff for intent and risk over the same range, for example git diff "${BASE}...HEAD".
• Note which layers are touched:
  • UI (React/components/styles)
  • Main process / backend services
  • IPC boundary / shared types
  • Tooling/scripts
  • Docs
  • Tests