gh-address

Address PR #$ARGUMENTS Comments

Systematically address review feedback on a pull request.

Tool Usage: This workflow uses the AskUserQuestion tool to clarify ambiguous feedback, confirm proposed fixes, and get approval before pushing changes.

Process

1. Fetch PR details and reviews:

   gh pr view $ARGUMENTS --json title,headRefName,state,reviews
   

2. Fetch review comments (inline code comments):

   gh api repos/{owner}/{repo}/pulls/$ARGUMENTS/comments
   

3. Fetch PR conversation (general discussion comments):

   gh api repos/{owner}/{repo}/issues/$ARGUMENTS/comments
   

4. Check for resolved/unresolved threads:

   gh api repos/{owner}/{repo}/pulls/$ARGUMENTS/comments --jq '[.[] | select(.in_reply_to_id == null)] | length'
   

5. Checkout PR branch (if not already on it):

   git fetch origin {headRefName}
   git checkout {headRefName}
   

6. Create checklist of all feedback items to address

7. For each comment:

   • Read and understand the feedback
   • Read the relevant content context

   If feedback is ambiguous, use the AskUserQuestion tool to clarify:

   • Quote the unclear comment
   • Present your interpretation options:
     • Option 1: "I interpret this as [interpretation A]"
     • Option 2: "I interpret this as [interpretation B]"
     • Option 3: "I need more context to understand"

   If you disagree with feedback, use the AskUserQuestion tool:

   • Option 1: "Implement the suggested change anyway"

   • Option 2: "Push back with explanation"

   • Option 3: "Discuss further before deciding"

   • Make the necessary changes

   • Commit with a descriptive message

8. Preview response and get approval using the AskUserQuestion tool:

   Before pushing, show the summary of changes and response comment:

   • Option 1: "Push changes and post this response" (Recommended)
   • Option 2: "Edit response comment first"
   • Option 3: "Make additional changes before pushing"