Gh Address Comments

GitHub PR Address Comments

Use This Skill When

• Need to address review comments on your open GitHub PR
• Want to systematically handle all feedback threads
• Making code changes in response to reviewer suggestions
• Need visibility into all pending comments before responding
• Want to batch-address multiple review items

When NOT to Use

• Responding directly on GitHub (can do manually)
• Complex discussions requiring back-and-forth debate
• Comments needing legal/compliance review
• Working on closed/merged PRs

Context: PR Feedback Workflow Maturity

Undeveloped: Manual review, ad-hoc responses, forget some comments.

Target: Fetch all comments, list with summaries, apply fixes after user selects which to address.

Optimized: Auto-categorize by type (bug, style, enhancement), suggest fixes for each, batch commit with reply threads.

Core Principle

Address feedback systematically. Fetch all comments, understand context, let user choose priorities, then apply fixes — reducing friction in PR review cycles.

Instructions

Step 1: Verify gh CLI Authentication

Check authentication status:

gh auth status

If not authenticated:

gh auth login
# Select GitHub.com
# Select SSH or HTTPS
# Authorize with browser

Verify workflow/repo scopes:

gh auth status --show-token  # Verify scopes include "repo" and "workflow"

Step 2: Locate Current PR

Find PR for current branch:

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

Or specify PR explicitly:

gh pr view 123 --json number,title,url,state
# or
gh pr view https://github.com/owner/repo/pull/123

Step 3: Fetch All Review Comments

Pull all comments and review threads:

# Run helper script (if available)
python scripts/fetch_comments.py

# Or manual approach:
gh pr view [PR] --json reviews --jq '.reviews[]'

Output includes:

• Reviewer name
• Comment text
• Status (approved, commented, changes requested)
• Threading structure

Step 4: Summarize and Prioritize Comments

Organize comments for user review:

# PR Comments to Address

## Review Thread 1: "Add error handling" (Changes Requested by @reviewer-name)
**Line**: src/utils.ts:42
**Comment**: "This function should handle null values gracefully"
**Context**: [Code snippet]
**Priority**: High — blocking approval
**Fix needed**: Add try-catch or validation

---

## Review Thread 2: "Typo in variable name" (Commented by @reviewer-name)
**Line**: src/types.ts:15
**Comment**: "Should this be `userAuthToken` instead of `userAuthTOKEN`?"
**Priority**: Medium — style
**Fix needed**: Rename variable

---

## Review Thread 3: "Nice refactoring!" (Approved by @reviewer-name)
**Status**: ✓ Approved
**Action**: No response needed

Step 5: Ask User Which Comments to Address

Present prioritized list:

Select which comments to address (enter numbers separated by comma):

[ 1] High: Add error handling (Line 42)
[ 2] Medium: Fix typo in variable name (Line 15)  
[ 3] Low: Consider adding JSDoc comment (Line 8)

Enter selection (e.g., "1,2"):

Step 6: Apply Fixes

For each selected comment:

1. Navigate to line/file

   code src/utils.ts:42  # Open editor at line
   

2. Make required changes

   • Apply fix (add error handling, rename variable, etc.)
   • Test locally if needed

3. Commit changes

   git add [files]
   git commit -m "Address review feedback: [comment theme]"
   git push
   

4. Reply to comment (optional)

   gh pr review [PR] --comment -b "Fixed: Added error handling for null values"
   

Step 7: Verify Updated Status

Check if review is now satisfied:

gh pr view [PR] --json reviewDecisions,statusCheckRollup

If approved:

gh pr merge [PR] --squash --delete-branch

Common Workflows

Address all blocking comments:

gh pr view [PR] --json reviews --jq '.reviews[] | select(.state=="CHANGES_REQUESTED")'
# Then select those for addressing

Reply to specific comment:

gh pr comment [PR] -b "Fixed in latest commit. Thanks for the feedback!"

Re-request review after fixing:

gh pr review [PR] --request-review @reviewer-name

Troubleshooting

Output

Deliver:

1. Organized comment list with context and priorities
2. User selections (which comments to address)
3. Applied changes with commit links
4. Updated PR status (approved/changes requested/etc.)