handle-pr-reviewer-feedback

Handle PR Reviewer Feedback

Reviews and responds to all reviewer comments on a GitHub pull request you authored, implementing valid feedback or explaining rejections with clear justification. On user approval it commits and pushes changes; whether replies are posted to GitHub is decided by should-post-to-github (based on ~/.sdlc/config.yaml), otherwise replies are drafted without posting.

For the reviewer-side flow (verifying that a PR author addressed your review comments), use handle-pr-author-feedback instead.

Prerequisites

• Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
• If no argument is provided, target the pull request from $PR_NUMBER (and $REPO).
• gh CLI authenticated with write access to the target repository
• PR number identifying an open pull request with at least one review comment
  • If $1 is provided, use it directly
  • If $1 is not provided, resolve the PR number with: gh pr list --head $(git branch --show-current) --json number --jq '.[0].number'

Skill attribution (GitHub)

Before posting any PR comment with gh, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = handle-pr-reviewer-feedback.

Workflow

Fetch PR comments ($1)
        |
        v
  For each comment
        |
        v
  Evaluate: actionable or not?
        |
        v
   Present outcome to user for approval
      /         \
  Approved     Rejected
     |             |
     v             v
  Implement       Skip
  changes
      |
      v
  Commit + push
  (always on approval)
      |
      v
     Reply to each comment thread
     with outcome (ghx), only if
     should-post-to-github allows

Steps

1. Fetch all PR review threads:

   ghx pr threads $1 --ids
   

2. For each comment, evaluate whether it is appropriate and actionable.
3. Present the evaluation and proposed action (implement or reject with explanation) to the user for approval.
4. For actionable comments that the user approved: implement the requested changes in the codebase.
5. Commit and push the changes (push is not gated):

   git add -A && git commit -m "<message>"
   git push
   

6. Decide whether to post replies: get the PR author (gh pr view $1 --repo <owner>/<repo> --json author --jq .author.login), then run ~/.agents/scripts/should-post-to-github --repo "<owner>/<repo>" --author "<PR_AUTHOR>". If it exits 0, reply to each comment thread with the outcome using ghx. For actionable comments where changes were implemented: reply with a brief summary and a link to the commit (e.g., "Done: added null guard for user in abc1234."). For non-actionable comments: reply with the rejection explanation. Use the thread IDs from step 1:

   ghx pr comment $1 --reply-thread <thread-id> --body "<outcome summary>"
   

   Append the Skill attribution footer to each reply. If the script exits 1, present the drafted replies to the user without posting.