Follow Up With Gemini

First: Get PR info using the agentTool wrapper:

./scripts/agents/tooling/agentTool.ts getPrInfo --fields number,title,url,headRefName

Extract number as PR_NUMBER for use in subsequent commands.

CRITICAL: Avoid Pending/Draft Reviews

DO NOT use any of these commands - they create pending reviews that Gemini will never see:

# WRONG - creates pending review
gh pr review --comment -b "message"
gh pr review --request-changes
gh api graphql -f query='mutation { addPullRequestReview(...) }'

ALWAYS use the agentTool wrapper to reply directly to comment threads - these are immediately visible:

# CORRECT - creates immediate comment reply
./scripts/agents/tooling/agentTool.ts replyToComment --number $PR_NUMBER --comment-id <comment_database_id> --body "message"

# For Gemini-specific replies with commit hash
./scripts/agents/tooling/agentTool.ts replyToGemini --number $PR_NUMBER --comment-id <comment_database_id> --commit <sha>

CRITICAL: Always Tag @gemini-code-assist

Every reply to a Gemini comment thread MUST include @gemini-code-assist in the message body. Without this tag, Gemini may not receive a notification and won't respond to your reply. This applies whether you're:

Confirming a fix was made
Explaining why the code is correct (disagreeing with feedback)
Asking for clarification
Deferring to an issue

Quota Exhaustion Fallback

If at any point Gemini responds with quota exhaustion ("You have reached your daily quota limit"):

Fall back to Codex review:

./scripts/agents/tooling/agentTool.ts solicitCodexReview

Skip waiting for Gemini's response
Return early with a message that Codex was used as fallback

Steps

Get the PR number (if not already retrieved):

./scripts/agents/tooling/agentTool.ts getPrInfo --fields number,title,url

CRITICAL: Verify commits are pushed to remote before replying.

Gemini and reviewers can only see commits that are visible on the remote. Before replying to ANY comment, verify your fix commits are actually pushed:

# Get the current branch
BRANCH=$(git branch --show-current)

# Fetch latest remote state
git fetch origin "$BRANCH"

# Compare local HEAD with remote - they MUST match
LOCAL_SHA=$(git rev-parse HEAD)
REMOTE_SHA=$(git rev-parse "origin/$BRANCH")

if [ "$LOCAL_SHA" != "$REMOTE_SHA" ]; then
  echo "ERROR: Local commits not yet pushed. Push first before replying."
  exit 1
fi

Do NOT proceed to reply until this verification passes. Replying with "Fixed in commit X" when commit X is not yet on remote creates confusion for reviewers.

Find unresolved Gemini review comments using the agentTool wrapper:
```
./scripts/agents/tooling/agentTool.ts getReviewThreads --number $PR_NUMBER --unresolved-only
```
This returns JSON array of unresolved review threads with:
- id: Thread node ID (for resolving)
- isResolved: Boolean (will be false due to --unresolved-only)
- comments: Array with {id, databaseId, author: {login}, body}
The wrapper handles pagination automatically.

For each unresolved comment that has been addressed and pushed (verified in step 2):

Reply using the agentTool wrapper:

# Use the databaseId from the comment you're replying to
./scripts/agents/tooling/agentTool.ts replyToComment --number $PR_NUMBER --comment-id <comment_database_id> \
  --body "Fixed in commit abc1234. @gemini-code-assist Please confirm this addresses your feedback."

# Or use the Gemini-specific helper for standard commit-fix replies:
./scripts/agents/tooling/agentTool.ts replyToGemini --number $PR_NUMBER --comment-id <comment_database_id> --commit abc1234

Include the commit SHA that fixed the issue (must be visible on remote per step 2)
Tag @gemini-code-assist and ask for confirmation

If deferring to an issue instead of fixing directly:

./scripts/agents/tooling/agentTool.ts replyToComment --number $PR_NUMBER --comment-id <id> \
  --body "@gemini-code-assist Tracked in #456 for follow-up. This is out of scope for the current PR."

If explaining why feedback doesn't apply (disagreeing):

./scripts/agents/tooling/agentTool.ts replyToComment --number $PR_NUMBER --comment-id <id> \
  --body "@gemini-code-assist The code is correct as written because [explanation]. Could you please re-review?"

Do NOT comment on the main PR thread. Only reply inside discussion threads.
Wait for Gemini's response: Poll for Gemini's reply every 30 seconds (up to 5 minutes):
- Use GraphQL to fetch the comment thread and check for new replies from gemini-code-assist
- To detect confirmation:
  1. Look for positive phrases: "looks good", "resolved", "satisfied", "fixed", "approved", "thank you", "lgtm"
  2. Ensure the response does NOT contain negative qualifiers: "but", "however", "still", "issue", "problem", "not yet", "almost"
  3. Only treat as confirmation if both conditions are met (positive phrase present AND no negative qualifiers)
- Example of false positive to avoid: "Thank you for the update, but I still see an issue" contains "thank you" but also "but" and "still" - do NOT resolve
Resolve satisfied comments: When Gemini confirms, resolve the thread:
```
./scripts/agents/tooling/agentTool.ts resolveThread --thread-id "<thread_node_id>"
```
Get thread IDs (id field) from the getReviewThreads output.
If Gemini requests further changes, do NOT resolve - return to /address-gemini-feedback.

Token Efficiency

The agentTool wrappers already use minimal JSON fields and handle output efficiently. Suppress git operations to avoid token waste: