pr-comments

PR Comments

Fetch and address review comments on the PR for the current branch.

Prerequisites

• gh CLI authenticated
• Current branch has an open PR

Step 1: Identify the PR

BRANCH=$(git branch --show-current)

Guard: skip if branch is main or master.

PR_NUM=$(gh pr view --json number -q .number)
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
OWNER=$(echo $REPO | cut -d/ -f1)
REPO_NAME=$(echo $REPO | cut -d/ -f2)

If no PR found, inform the user and stop.

Step 2: Fetch review data

Run these in parallel:

# Inline code review comments (threaded)
gh api "repos/$REPO/pulls/$PR_NUM/comments" --paginate \
  --jq '.[] | {id, path, line, body, user: .user.login, created_at, in_reply_to_id, diff_hunk}'

# Top-level reviews (approval / request-changes + body)
gh api "repos/$REPO/pulls/$PR_NUM/reviews" --paginate \
  --jq '.[] | {id, user: .user.login, state, body}'

# General PR discussion comments
gh api "repos/$REPO/issues/$PR_NUM/comments" --paginate \
  --jq '.[] | {id, user: .user.login, body, created_at}'

Step 3: Group into threads

• A comment with in_reply_to_id: null starts a thread.
• Replies link to their parent via in_reply_to_id.
• Track: file, line, diff hunk, author, all replies in order.

Step 4: Classify

Bot comments (login ends with [bot]): summarise briefly, only surface actionable failures.

Human comments: full treatment in Step 5.

Step 5: For each unresolved human comment

1. Show context: file, line, diff hunk, comment body.
2. Read the current file at the referenced location.
3. Summarise the reviewer's concern in one sentence.
4. Assess: Is the feedback valid? Use your judgement — reviewers may lack context or be wrong.
5. Propose a concrete action and ask the user:
   • Fix → apply the code change (do NOT commit)
   • Reply → post a reply via gh api
   • Skip → move on

For already-resolved threads, present as a summary group and ask if user wants to revisit.