Process PR Reviews

This workflow supports both CodeRabbit and Codex PR review signals.

CodeRabbit Reviews

“Real review feedback” is strictly defined as:

• inline review comments
• not a review summary
• not a nitpick

Nitpick comments from CodeRabbit must always be ignored to avoid unnecessary noise.

There is no need to analyze the comment content itself.

Data sources

The CodeRabbit workflow only needs these two sources:

1. PR review comments

   gh api --paginate repos/<owner>/<repo>/pulls/<pr_number>/comments
   

   This is the authoritative source for real inline comments.

2. PR reviews

   gh api --paginate repos/<owner>/<repo>/pulls/<pr_number>/reviews
   

   This is only used to identify and exclude review summaries / nitpick summaries. It is not used to extract the final result.

Do not treat these as primary sources:

• gh pr view ...
• gh api repos/<owner>/<repo>/issues/<pr_number>/comments

Reason: they are not the authoritative source for actionable inline comments.

Workflow

0. Optional: fetch review thread IDs early if resolve/dismiss may be needed

If the user may ask you to resolve review conversations after triaging them, fetch review thread IDs as soon as you know the PR number:

gh api graphql -f query='query { repository(owner: "<owner>", name: "<repo>") { pullRequest(number: <pr_number>) { reviewThreads(first: 100) { nodes { id isResolved comments(first: 20) { nodes { databaseId path line author { login } body } } } } } } }'

This is not a primary source for actionable review feedback. It is only for mapping inline comments to resolvable thread IDs.

Recommendation:

• If the user only wants to view/list/count review feedback, this step is optional.
• If the user may want to resolve conversations, doing this early is usually more convenient because you can map comment databaseId / path / line to thread IDs in one pass.