poitch/pr-comments

Address PR Comments

Pull all review comments from the current GitHub pull request and address each one by making the necessary code changes.

Step 1: Identify the PR

If the user provided a PR number as $ARGUMENTS, use that. Otherwise, detect the PR for the current branch:

gh pr view --json number,title,url,headRefName

If no PR is found, inform the user and stop.

Step 2: Fetch all review comments

Get all review comments (file-level comments, not general PR comments) using:

gh api repos/{owner}/{repo}/pulls/{number}/comments --paginate --jq '.[] | {id, path, line, original_line, side, body, diff_hunk, subject_type, user: .user.login, created_at, in_reply_to_id}'

Also fetch review threads via GraphQL to understand resolved vs unresolved status (note: gh pr view --json does NOT support reviewThreads):

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

Filter the results to only unresolved threads (isResolved == false). The id field on each thread node is the GraphQL node ID needed to resolve the thread later.

Step 3: Filter and organize

• Only address unresolved comment threads - skip any threads that are already resolved.
• Skip reply comments (those with in_reply_to_id set) - only process top-level comments in each thread.
• Group comments by file path for efficient processing.
• Present a summary to the user showing each comment with:
  • File path and line number
  • Who wrote the comment
  • The comment body
  • The relevant code context (from diff_hunk)

Step 4: Address each comment

For each unresolved comment:

1. Read the relevant file to understand the full context around the commented line.
2. Analyze the comment to determine what change is being requested.
3. Make the code change using the Edit tool.
4. Resolve the comment thread on GitHub using the GraphQL API:

   gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "<thread_node_id>"}) { thread { isResolved } } }'
   

   To get the thread node ID, include id (the GraphQL node ID) when fetching review threads in Step 2.
5. Briefly explain what you changed and why.

If a comment is unclear or requires a design decision, flag it to the user instead of guessing. Do NOT resolve these threads.

Step 5: Summary

After addressing all comments, provide a summary:

• List each comment and what was done to address it
• Note any comments that were skipped or need human input
• Remind the user to review the changes before committing