address-review-comments

# Address Review Comments

## Workflow

- [ ] Identify target PR and ensure correct branch
- [ ] Fetch review comments
- [ ] Clarify ambiguous feedback with user
- [ ] Fix each comment (one commit per fix)
- [ ] Confirm changes with user
- [ ] Push changes
- [ ] Reply to review threads with commit references

## Step 1: Identify Target PR

### If given a PR URL (e.g., `https://github.com/owner/repo/pull/123`)

Extract owner, repo, and PR number from the URL.

Check current repo matches:
```bash
gh repo view --json nameWithOwner --jq '.nameWithOwner'
```

Check out the PR branch:
```bash
gh pr checkout 123        # normal checkout
gh pr checkout 123 --force  # if local changes conflict
```

### If no URL provided

Find PR for current branch:
```bash
gh pr view --json number,title,url,headRefName
```

If no PR exists for current branch, ask the user which PR to address.

## Step 2: Fetch Comments

### Get review comments (code review threads)

Use the `github-mcp-server-pull_request_read` tool:
```
method: "get_review_comments"
owner: "<repo_owner>"
repo: "<repo_name>"
pullNumber: <pr_number>
```

Response includes `reviewThreads` with:
- `IsResolved`: filter for `false` to get unresolved comments
- `IsOutdated`: whether the code location has changed
- `Comments.Nodes[]`: array with `Body`, `Path`, `Line`, `Author`

### Get general PR comments (conversation tab)

Use the `github-mcp-server-pull_request_read` tool:
```
method: "get_comments"
owner: "<repo_owner>"
repo: "<repo_name>"
pullNumber: <pr_number>
```

## Step 3: Review and Clarify

Present unresolved comments to the user. For each comment, summarize:
- File and line number
- Reviewer's feedback
- Your proposed fix

Ask clarifying questions if:
- The feedback is ambiguous
- Multiple valid solutions exist
- The fix might affect other code

## Step 4: Fix Each Comment

For each review comment:

1. Make the code change
2. Validate the change (run build/tests as appropriate)
3. Create a focused commit:
```bash
git