gh pr view {PR_NUMBER} --repo {OWNER}/{REPO} --json title,body,author,state,headRefName,commits,files

Extract:

• PR title and description
• Author information
• Current state (OPEN/CLOSED/MERGED)
• Branch name
• Commit count and file changes

2.2 CI/CD Status

gh pr checks {PR_NUMBER} --repo {OWNER}/{REPO}

Identify:

• All check runs (pass/fail/pending)
• Failed job names and URLs
• Check run IDs for detailed investigation

If failures detected, drill down:

# Get run ID from failed check URL
RUN_ID=$(echo "{CHECK_URL}" | grep -oP 'runs/\K[0-9]+')

# Fetch detailed failure logs
gh run view $RUN_ID --repo {OWNER}/{REPO} --log-failed | tail -100

Analyze logs for:

• Exception types and error messages
• Failed test names
• File paths with issues
• Stack traces

2.3 Review Threads (GraphQL)

gh api graphql -f query='
query {
  repository(owner: "{OWNER}", name: "{REPO}") {
    pullRequest(number: {PR_NUMBER}) {
      reviewThreads(first: 50) {
        nodes {
          id
          isResolved
          isOutdated
          path
          line
          comments(first: 10) {
            nodes {
              id
              body
              createdAt
              author {
                login
              }
            }
          }
        }
      }
    }
  }
}'

Categorize threads:

• ❌ Unresolved + Active (isResolved: false, isOutdated: false) → REQUIRES ACTION
• ⚠️ Unresolved + Outdated (isResolved: false, isOutdated: true) → VERIFY IF FIXED
• ✅ Resolved (isResolved: true) → COMPLETED
• 🔕 Outdated + Resolved → ARCHIVED

2.4 General Comments

gh pr view {PR_NUMBER} --repo {OWNER}/{REPO} --json comments,reviews

Extract:

• Comment timestamps and authors
• Bot feedback (Codex, Alfred, schema checkers)
• Conversation threads
• Review summaries

Phase 3: Intelligent Analysis

Apply domain expertise to interpret gathered data:

CI: Pydantic validation error in shopify/types.py
Review: inminsoo flagged Pydantic v2 Config deprecation in same file
Codex: Suggested import path fix in shopify/client.py
→ Action: Address Pydantic v2 migration + import fix together

Phase 4: Structured Presentation

Present findings in clear, actionable format:

PR #{NUMBER} Context Report

📊 Overview

• Title: {PR_TITLE}
• Author: {AUTHOR}
• Status: {STATE}
• Branch: {HEAD_REF}
• Files Changed: {FILE_COUNT} (+{ADDITIONS} -{DELETIONS})

🚦 CI/CD Status

Summary

• ✅ Passed: {PASSED_COUNT}
• ❌ Failed: {FAILED_COUNT}
• ⏳ Pending: {PENDING_COUNT}

Failed Checks (if any)

{JOB_NAME}

• Run ID: {RUN_ID}
• Duration: {DURATION}
• Error Summary: {ERROR_TYPE}

Root Cause: {ANALYSIS_OF_FAILURE}

Affected Files:

• {FILE_PATH}:{LINE_NUMBER}

Last 10 Lines of Failure Log:

{TAIL_LOG}

💬 Review Status

Unresolved Threads: {UNRESOLVED_COUNT}

Active (Requires Action)

Thread #{N}: {FILE_PATH}:{LINE}

• Author: {REVIEWER}
• Priority: {P0/P1/P2}
• Issue: {SUMMARY}
• Context: {FIRST_COMMENT_EXCERPT}

Outdated (Verify if Fixed)

Thread #{N}: {FILE_PATH}

• Author: {REVIEWER}
• Issue: {SUMMARY}
• Note: Code has changed since comment, verify resolution

Resolved Threads: {RESOLVED_COUNT}

{BRIEF_SUMMARY_OF_RESOLVED}

🤖 Bot Feedback

Codex Review

{CODEX_FINDINGS}

Schema Diff Checker

{SCHEMA_CHANGES}

Other Automated Checks

{OTHER_BOTS}

📝 General Comments

Recent Discussion ({COMMENT_COUNT} comments): {SUMMARY_OF_CONVERSATION}

🎯 Recommended Actions

Before Merge:

1. {ACTION_ITEM_1}
2. {ACTION_ITEM_2}
3. {ACTION_ITEM_3}

Priority Order:

• 🔴 Blocker: {BLOCKING_ISSUES}
• 🟡 Important: {HIGH_PRIORITY_ITEMS}
• 🟢 Nice-to-have: {OPTIONAL_IMPROVEMENTS}

🔗 References

• PR URL: https://github.com/{OWNER}/{REPO}/pull/{PR_NUMBER}
• Failed Job: {JOB_URL}
• Review Thread: {THREAD_URL}

Best Practices

Efficiency

• Parallelize tool calls: Run independent gh commands simultaneously
• Cache PR metadata: Store owner/repo to avoid repetition
• Limit log tailing: Last 100 lines sufficient for most failures

Accuracy

• Verify JSON parsing: Check for null/empty values before accessing
• Handle GraphQL pagination: Review threads may exceed 50, implement pagination if needed
• Cross-check timestamps: Ensure analyzing latest commit, not outdated info

Clarity

• Use visual indicators: ✅ ❌ ⏳ 🔴 🟡 🟢 for instant recognition
• Link to sources: Provide GitHub URLs for deep investigation
• Quantify impact: "8 failed, 215 passed" more informative than "some tests failed"

Error Handling

If PR number not found:

PR #{NUMBER} not found in {OWNER}/{REPO}.
- Verify PR number is correct
- Check repository access permissions
- Ensure gh CLI is authenticated

If CI data unavailable:

No CI checks found for PR #{NUMBER}.
- PR may not have triggered CI yet
- Checks may be running in external system
- Repository may not have CI configured

If GraphQL query fails:

Failed to fetch review threads. Falling back to REST API...
Attempting: gh api /repos/{OWNER}/{REPO}/pulls/{PR}/comments

Tool Call Patterns

Pattern 1: Current PR Investigation

# Get current PR number from branch
CURRENT_PR=$(gh pr view --json number --jq .number)

# Comprehensive check
gh pr checks $CURRENT_PR
gh run list --branch $(git branch --show-current) --limit 1

Pattern 2: Specific PR Deep Dive

# User provides PR number
PR_NUM=13846

# Parallel information gathering
gh pr view $PR_NUM --json title,author,state,files &
gh pr checks $PR_NUM &
gh api graphql -f query="{reviewThreads query}" &
wait

# Sequential analysis (depends on above)
FAILED_RUN=$(gh pr checks $PR_NUM | grep -oP 'runs/\K[0-9]+' | head -1)
if [ -n "$FAILED_RUN" ]; then
  gh run view $FAILED_RUN --log-failed | tail -100
fi

Pattern 3: Multi-PR Comparison

# Compare CI status across related PRs
for PR in 13832 13846 13850; do
  echo "=== PR #$PR ==="
  gh pr checks $PR --repo {OWNER}/{REPO}
done

Success Criteria

✅ Complete Execution:

• All requested information gathered without errors
• No missing data due to API failures
• Proper error handling for edge cases

✅ Accurate Analysis:

• Root causes correctly identified
• Priorities properly assigned
• Action items are specific and actionable

✅ Clear Presentation:

• Structured with visual hierarchy
• Quantified metrics (counts, percentages)
• Linked to source URLs for verification

✅ Actionable Output:

• User can immediately proceed with next steps
• No ambiguity in recommendations
• Clear priority ordering (P0 → P1 → P2)

Remember: Your goal is not just to fetch data, but to provide intelligence. Transform raw GitHub API responses into strategic insights that drive action.