WIP [2026-06-08 11:01:20]

Signed-off-by: Derek Misler <derek.misler@docker.com>

Author: derekmisler

.github/workflows/review-pr.yml

@@ -159,7 +159,7 @@ jobs:
         (needs.resolve-context.result == 'success' && needs.resolve-context.outputs.trigger-event == 'pull_request')
       )
     runs-on: ubuntu-latest
-    timeout-minutes: 35
+    timeout-minutes: 50
     permissions:
       contents: read
       pull-requests: write
@@ -224,6 +224,18 @@ jobs:
             echo "⏭️ Not a /review command, skipping"
           fi
 
+      - name: Post /review deprecation notice
+        if: github.event_name == 'issue_comment' && steps.command.outputs.is_review == 'true'
+        shell: bash
+        env:
+          GH_TOKEN: ${{ steps.resolve-token.outputs.token }}
+          PR_NUMBER: ${{ steps.resolve-context.outputs.pr-number }}
+          REPOSITORY: ${{ github.repository }}
+        run: |
+          gh api "repos/$REPOSITORY/issues/$PR_NUMBER/comments" \
+            -f body="👋 **Heads up:** The \`/review\` command is deprecated. Please re-request a review from \`docker-agent\` in the PR sidebar instead. This review will still complete normally." \
+            2>&1 || echo "::warning::Failed to post /review deprecation notice"
+
       - name: Classify trigger type
         id: trigger-type
         shell: bash

README.md

@@ -214,7 +214,7 @@ jobs:
 
 ### PR Review Workflow
 
-For comprehensive documentation on setting up AI-powered PR reviews, including features like requesting a review from `docker-agent`, automatic reviews, the `/review` command, feedback learning, and customization options, see the **[PR Review documentation](review-pr/README.md)**.
+For comprehensive documentation on setting up AI-powered PR reviews, including features like automatic reviews, requesting a review from `docker-agent`, feedback learning, and customization options, see the **[PR Review documentation](review-pr/README.md)**.
 
 ### Manual Trigger with Inputs
 

review-pr/README.md

@@ -2,7 +2,7 @@
 
 AI-powered pull request review using a multi-agent system. Analyzes code changes, posts inline comments, and learns from your feedback.
 
-> **Primary trigger:** Add `docker-agent` as a reviewer in the PR sidebar — the review starts automatically. The `/review` comment is always available for re-triggering.
+> **Primary trigger:** Add `docker-agent` as a reviewer in the PR sidebar — the review starts automatically. To re-trigger a review, re-request a review from `docker-agent` in the PR sidebar. The `/review` comment still works but is deprecated.
 
 ## Quick Start
 
@@ -152,7 +152,7 @@ The `pull_request` trigger types in your calling workflow control how often revi
 pull_request:
   types: [opened, ready_for_review, review_requested]
 ```
-Reviews run when a PR is opened or marked ready for review. After the initial review, further `pull_request`-triggered reviews only run when `docker-agent` is explicitly re-requested as a reviewer. Use `/review` to re-trigger ad-hoc at any time.
+Reviews run when a PR is opened or marked ready for review. After the initial review, further `pull_request`-triggered reviews only run when `docker-agent` is explicitly re-requested as a reviewer. Re-request a review from `docker-agent` in the PR sidebar to re-trigger at any time. The `/review` comment still works but is deprecated.
 
 **Mode A — continuous re-review on every push:**
 ```yaml
@@ -174,7 +174,7 @@ with:
 | ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
 | Request review from `docker-agent`   | **Primary trigger.** Add `docker-agent` as a reviewer in the PR sidebar — review starts automatically, shown as a check run.            |
 | PR opened/ready                      | Auto-reviews when a PR is opened or marked ready for review.                                                                             |
-| `/review` comment                    | Re-trigger a review, or trigger manually when auto-review hasn't run (e.g. after a force-push). Shows as a check run if `checks: write` is granted. |
+| ~~`/review`~~ _(deprecated)_         | Re-trigger a review, or trigger manually when auto-review hasn't run (e.g. after a force-push). Shows as a check run if `checks: write` is granted. |
 | Reply to review comment              | Responds in-thread and captures feedback to improve future reviews.                                                                      |
 | `@docker-agent` mention              | Answers questions and clarifies review findings. Works in both PR-level issue comments and inline file-line review comments, including on fork PRs (via the trigger workflow). |
 

review-pr/action.yml

@@ -759,7 +759,7 @@ runs:
       with:
         agent: ${{ env.ACTION_PATH }}/agents/pr-review.yaml
         prompt: ${{ steps.context.outputs.review_prompt }}
-        timeout: "1800"  # 30 min — allows complex reviews to complete; lock TTL (600 s) is intentionally shorter
+        timeout: "2700"  # 45 min — allows complex reviews to complete; lock TTL (600 s) is intentionally shorter
         anthropic-api-key: ${{ inputs.anthropic-api-key }}
         openai-api-key: ${{ inputs.openai-api-key }}
         google-api-key: ${{ inputs.google-api-key }}
@@ -816,6 +816,7 @@ runs:
         VERBOSE_LOG_FILE: ${{ steps.run-review.outputs.verbose-log-file }}
         SKIP_REASON: ${{ steps.lock-check.outputs.skip-reason }}
         LOCK_AGE: ${{ steps.lock-check.outputs.lock-age }}
+        CHUNK_COUNT: ${{ steps.chunk-diff.outputs.chunk_count }}
       run: |
         REVIEW_URL="https://github.com/$REPOSITORY/pull/$PR_NUMBER"
         echo "review-url=$REVIEW_URL" >> $GITHUB_OUTPUT
@@ -829,13 +830,18 @@ runs:
         elif [ -z "$EXIT_CODE" ]; then
           STATUS="⏭️ **Review skipped** — agent did not run"
         elif [ "$EXIT_CODE" = "124" ]; then
-          # Timeout (SIGKILL after 1800 s) — provide actionable guidance
-          STATUS="⏱️ **Review timed out** (exit code: 124, limit: 1800 s)"
-          TIMEOUT_NOTE="- **Exit code:** 124 (SIGKILL — 1800 s timeout)"
-          TIMEOUT_NOTE+=$'\n'"- **Timeout limit:** 1800 s"
+          # Timeout (SIGKILL after 2700 s) — provide actionable guidance
+          STATUS="⏱️ **Review timed out** (exit code: 124, limit: 2700 s)"
+          TIMEOUT_NOTE="- **Exit code:** 124 (SIGKILL — 2700 s timeout)"
+          TIMEOUT_NOTE+=$'\n'"- **Timeout limit:** 2700 s"
           TIMEOUT_NOTE+=$'\n'"- Verbose log artifact (${VERBOSE_LOG_FILE}) uploaded for debugging."
+          if [ "${CHUNK_COUNT:-1}" = "1" ]; then
+            TIMEOUT_BODY="⏱️ **PR Review Timed Out** — The review agent hit the 2700 s time limit. The diff is small (1 chunk), so this may be an agent loop rather than a large-diff problem. Re-request a review from \`docker-agent\` to retry. If it times out again, download the verbose log artifact for details."
+          else
+            TIMEOUT_BODY="⏱️ **PR Review Timed Out** — The review agent hit the 2700 s time limit. This usually happens on large or complex diffs. Re-request a review from \`docker-agent\` to retry — if it times out again, consider splitting the PR into smaller pieces."
+          fi
           if ! gh api "repos/$REPOSITORY/issues/$PR_NUMBER/comments" \
-            -f body="⏱️ **PR Review Timed Out** — The review agent hit the 1800 s time limit before completing. This usually happens on large or complex diffs. You can re-trigger with \`/review\` — if it times out again, consider splitting the PR into smaller pieces." \
+            -f body="$TIMEOUT_BODY" \
             2>&1; then
             echo "::warning::Failed to post timeout comment to PR"
           fi

review-pr/agents/pr-review.yaml

@@ -324,6 +324,7 @@ agents:
 
   drafter:
     model: sonnet
+    max_iterations: 40
     description: Bug Hypothesis Generator
     add_date: true
     instruction: |
@@ -597,6 +598,7 @@ agents:
 
   verifier:
     model: sonnet
+    max_iterations: 20
     description: Hypothesis Verifier
     add_date: true
     instruction: |