feat(code-review): batch review comments into a single agent prompt

[adboio]

problem

closes #1827

when giving agent feedback from a diff, users can only submit one comment at a time

changes

allows batching comments into a "review" for the agent

testing

manually

[greptile-apps]

Comments Outside Diff (2)

1. apps/code/src/renderer/features/code-review/utils/reviewPrompts.ts, line 1184 (link)

   Numbered list in prompt violates "no numbers in list" rule

   The batch prompt uses ${idx + 1}. to enumerate comments. The team rule is to avoid numbered lists in prompts to prevent confusion when user responses contain numbers themselves — use bullets or letters instead.

   Rule Used: In prompts, avoid using numbers in lists to preven... (source)

   Learned From
   PostHog/posthog#31624

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: apps/code/src/renderer/features/code-review/utils/reviewPrompts.ts
   Line: 1184
   
   Comment:
   **Numbered list in prompt violates "no numbers in list" rule**
   
   The batch prompt uses `${idx + 1}.` to enumerate comments. The team rule is to avoid numbered lists in prompts to prevent confusion when user responses contain numbers themselves — use bullets or letters instead.
   
   
   
   **Rule Used:** In prompts, avoid using numbers in lists to preven... ([source](https://app.greptile.com/review/custom-context?memory=1dd45b94-c307-4dd0-a025-5aa16059229b))
   
   **Learned From**
   [PostHog/posthog#31624](https://github.com/PostHog/posthog/pull/31624)
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

2. apps/code/src/renderer/features/code-review/components/PendingReviewBar.tsx, line 563-565 (link)

   Drafts cleared before send succeeds

   clearDrafts is called before sendPromptToAgent, so if the send throws the queued comments are silently lost. The PR description says drafts should clear only on a successful send. Swapping the order aligns implementation with stated intent.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: apps/code/src/renderer/features/code-review/components/PendingReviewBar.tsx
   Line: 563-565
   
   Comment:
   **Drafts cleared before send succeeds**
   
   `clearDrafts` is called before `sendPromptToAgent`, so if the send throws the queued comments are silently lost. The PR description says drafts should clear only on a successful send. Swapping the order aligns implementation with stated intent.
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
apps/code/src/renderer/features/code-review/utils/reviewPrompts.ts:1184
**Numbered list in prompt violates "no numbers in list" rule**

The batch prompt uses `${idx + 1}.` to enumerate comments. The team rule is to avoid numbered lists in prompts to prevent confusion when user responses contain numbers themselves — use bullets or letters instead.

```suggestion
      return `- In file <file path="${escapedPath}" />, ${lineRef} (${sideLabel}):\n${indented}`;
```

### Issue 2 of 3
apps/code/src/renderer/features/code-review/components/InteractiveFileDiff.tsx:375-389
**`handleEditDraft` duplicated across `PatchDiffView` and `FilesDiffView`**

The same callback — look up the draft by id, call `openCommentForEdit` — is copy-pasted verbatim into both components. Extracting it into the shared `useCommentState` hook (or a small dedicated hook that takes `fileDrafts` and `openCommentForEdit`) would keep this logic OnceAndOnlyOnce and make future changes to the edit flow easier to track.

### Issue 3 of 3
apps/code/src/renderer/features/code-review/components/PendingReviewBar.tsx:563-565
**Drafts cleared before send succeeds**

`clearDrafts` is called before `sendPromptToAgent`, so if the send throws the queued comments are silently lost. The PR description says drafts should clear only on a successful send. Swapping the order aligns implementation with stated intent.

```suggestion
    sendPromptToAgent(taskId, prompt);
    clearDrafts(taskId);
```

_{Reviews (1): Last reviewed commit: "feat(code-review): batch review comments..." | Re-trigger Greptile}

[adboio]

• feat(code-review): batch review comments into a single agent prompt #1965 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/code-review/components/CommentAnnotation.tsx:88-92
The user's explicit opt-out of batching is never persisted. When the user unchecks "Add to review" and sends a comment directly, `setBatchEnabled(taskId, false)` is never called. Because `isBatchEnabled` falls back to `(drafts.length > 0)` when no explicit value is stored, the next comment box will open with the batch checkbox re-checked as long as pending drafts exist — overriding the user's choice every time.

```suggestion
    setBatchEnabled(taskId, false);
    onDismiss();
    sendPromptToAgent(
      taskId,
      buildInlineCommentPrompt(filePath, startLine, endLine, side, text),
    );
```

_{Reviews (2): Last reviewed commit: "fix(code-review): address PR feedback on..." | Re-trigger Greptile}

[arthurdedeus]

lgtm! low-context review, though (codebase-wise)

[arthurdedeus]

nice!!