Cap diff size with summarization fallback in AI code review

[google-labs-jules]

Add a tiered guard to the code review orchestrator. If a git diff exceeds 40,000 characters, the AI review is skipped and a manual human review request is posted instead. This prevents cost spikes from large refactors and ensures that the model doesn't provide feedback based on incomplete diff context.

Fixes #2580

---

PR created automatically by Jules for task 8026114155747465991 started by @arii

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[github-actions]

🐙 GitHub Models Code Review

Powered by GitHub Models

Reviewing: PR #2590

Code Review Feedback

HIGH SEVERITY ISSUES

1. Missing Required Property in Error Return (Blocking)

   In getCodeDiffSummary, the error catch block returns:

   return { files: [], diffContext: '', prGoal: undefined, isTruncated: false };

   However, the CodeReviewSummary interface defines prGoal as optional (prGoal?: string;), but isTruncated is also optional (isTruncated?: boolean;). The previous implementation returned { files: [], diffContext: '' } (without prGoal or isTruncated). Now, the function always returns isTruncated (true or false), but the interface marks it as optional.

   Blocking Issue:
   The interface and implementation are inconsistent. If consumers expect isTruncated to always be present, it should not be optional. If it is optional, the function should not always return it. This can cause runtime bugs if downstream code expects isTruncated to always exist.

   Action:

   • Either make isTruncated required in the interface (isTruncated: boolean;), or
   • Only include isTruncated in the return object when it is relevant (i.e., when the diff is truncated).

   This is a blocking type mismatch between interface and implementation.

2. Incorrect Return Type for Error Case (Blocking)

   In the error catch block:

   return { files: [], diffContext: '', prGoal: undefined, isTruncated: false };

   The interface for CodeReviewSummary is:

   export interface CodeReviewSummary {
     files: string[];
     diffContext: string;
     prGoal?: string;
     isTruncated?: boolean;
   }

   If prGoal is undefined, and downstream code expects a string (since in normal flow it is always a string), this can cause runtime errors. The previous implementation returned { files: [], diffContext: '' } (no prGoal). Now, it returns prGoal: undefined. If downstream code does not handle undefined, this is a blocking bug.

   Action:

   • Ensure that all consumers of prGoal handle the undefined case, or
   • Remove prGoal: undefined from the error return, since it is optional.

   This is a blocking issue if downstream code does not handle undefined.

---

Summary of Blocking Issues:

• The interface and implementation for isTruncated and prGoal are inconsistent, leading to potential runtime bugs and type errors.

---

[VERDICT: FAIL]

---

Generated by github-models-code-review

[github-actions]

🚀 Deployment Details (Last updated: Jun 19, 2026, 11:19 AM PST)

🚀 Pushed to gh-pages; publish in progress

• Preview URL: https://arii.github.io/tech-dancer/jules-large-diff-guard-8026114155747465991/
• Preview Dashboard: https://arii.github.io/tech-dancer/previews/index.html
• Commit SHA: 093a453
• Marker File: verify here

[arii]

Hi! This PR has merge conflicts with the base branch.

To fix this, please follow these steps:

1. Ensure your local main branch is up to date.
2. Switch back to your feature branch.
3. Merge main into your branch.
4. Resolve the conflicts in the files marked by Git, then stage the resolved files.
5. Complete the merge commit.
6. Push the resolved branch to origin.

Alternatively, you can rebase your branch onto main and resolve conflicts step-by-step. Let us know if you need any help!

[arii]

ANTI-AI-SLOP\n\n\n## FINDINGS\n

\n\n## FINAL RECOMMENDATION\n<Approved | Approved with Minor Changes | Not Approved>\n\n

Inline Comments (Fallback due to Github line resolution errors)

• :1:

[arii]

ANTI-AI-SLOP\n\n\n## FINDINGS\n

\n\n## FINAL RECOMMENDATION\n<Approved | Approved with Minor Changes | Not Approved>\n\n

Inline Comments (Fallback due to Github line resolution errors)

• :1:

[arii]

Automated Review for PR #2590

CI Status: All checks passing.

FINAL RECOMMENDATION

Approved

[arii]

Automated Review for PR #2590

CI Status: All checks passing.

Recommendation: Everything looks good from a CI perspective. Ready for manual review/merge if no other concerns.

FINAL RECOMMENDATION

Approved

[arii]

Comprehensive Review for PR #2590

CI Status: All checks passing.

Recommendation: Everything looks good from a CI perspective. All tests and linters pass. Ready for manual review/merge if no other concerns.

FINAL RECOMMENDATION

Approved

[arii]

@jules-fix-ci

[github-actions]

🤖 Jules is on it!

Initialized autonomous repair session (sessions/16242866451752128105) for branch jules-large-diff-guard-8026114155747465991.