Follow-up on PR review comment replies. Use when someone says "check if they addressed my comments", "follow up on PR feedback", "did they fix what I asked?", or when evaluating developer responses to review feedback.
From claude-code-handbooknpx claudepluginhub lioartoil/claude-code-handbookThis skill is limited to using the following tools:
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
You are reviewing developer responses to previous code review comments.
Arguments: $ARGUMENTS
Parse the first URL as the PR URL, remaining URLs as discussion threads to review.
/pr-followup https://github.com/org/repo/pull/42 https://github.com/org/repo/pull/42#discussion_r1234567 https://github.com/org/repo/pull/42#discussion_r1234568
This reviews PR #42 and evaluates responses to two specific discussion threads.
!gh pr view --json number,title,state,reviewDecision 2>/dev/null || echo "Fetch PR info manually"
!gh pr diff --name-only 2>/dev/null | head -20 || echo "No diff available"
!gh pr view --comments --json comments --jq '.comments[-5:]' 2>/dev/null || echo "No comments"
For each discussion URL provided:
gh apiDeveloper responded to your comment?
├── YES: Did they make code changes?
│ ├── YES: Does the change fix the original concern?
│ │ ├── YES → RESOLVED
│ │ └── NO → PENDING (explain what's still wrong)
│ └── NO: Did they provide valid reasoning?
│ ├── YES: Is the reasoning technically sound?
│ │ ├── YES → ACCEPTABLE_ALTERNATIVE
│ │ └── NO → DISAGREED (explain why)
│ └── NO → PENDING (request code change or reasoning)
└── NO → PENDING (no response yet)
# Extract discussion ID from URL and fetch
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}
| Error | Cause | Solution |
|---|---|---|
| "Fetch PR info manually" | Wrong directory or PR not found | Verify PR URL and run gh pr checkout |
| Discussion URL 404 | Comment was deleted or resolved | Note as "DELETED — cannot evaluate" |
| No developer response | Comment hasn't been addressed yet | Mark as PENDING with "Awaiting response" |
| gh api rate limit | Too many API calls | Wait 60 seconds, retry with --paginate |
| Closed/merged PR | PR state changed since review | Note current state, evaluate responses anyway |
| # | Original Issue | Developer Response | Resolution |
|---|---|---|---|
| 1 | [Your comment summary] | [Their response] | RESOLVED / PENDING / DISAGREED |
| 2 | [Your comment summary] | [Their response] | RESOLVED / PENDING / DISAGREED |
Resolved - No Action Needed:
Needs Follow-up Comment:
# Reply to discussion
gh api repos/{owner}/{repo}/pulls/{pr}/comments/{comment_id}/replies \
-f body="[Your follow-up response]"
New Issues to Raise:
# New inline comment if needed
gh api repos/{owner}/{repo}/pulls/{pr}/comments \
-f body="[New concern]" \
-f path="[file]" \
-f line=[line] \
-f commit_id="$(gh pr view --json headRefOid --jq '.headRefOid')"
Based on the follow-up review:
[Any decisions made, trade-offs accepted, or items deferred to future work]