respond-to-pr-review
Fetch, analyze, and respond to PR review comments. Use when asked to check PR comments, address review feedback, respond to reviewers, or fix issues raised in code reviews.
When & Why to Use This Skill
This Claude skill streamlines the GitHub Pull Request workflow by automatically fetching, analyzing, and responding to review comments. It empowers developers to efficiently address feedback, implement suggested code changes, and maintain clear communication with reviewers by posting AI-signed responses and resolving discussion threads directly through the GitHub API.
Use Cases
- Automated Feedback Implementation: Quickly address and fix code style, logic issues, or documentation suggestions raised during a PR review without manual context switching.
- PR Comment Summarization: Generate a concise overview of all unresolved review comments, categorized by file and severity, to help developers prioritize their workload.
- Streamlined Reviewer Communication: Automatically reply to review threads with detailed explanations of the fixes applied and resolve the threads to keep the PR status clean and ready for merging.
| name | respond-to-pr-review |
|---|---|
| description | Fetch, analyze, and respond to PR review comments. Use when asked to check PR comments, address review feedback, respond to reviewers, or fix issues raised in code reviews. |
Respond to PR Review
Fetch and respond to review comments on pull requests.
Instructions
1. Determine PR number
If not provided, detect from current branch:
gh pr view --json number -q .number
2. Fetch review comments
gh api repos/{owner}/{repo}/pulls/{pr}/comments
3. Fetch review thread IDs and resolution status
gh api graphql -f query='
query {
repository(owner: "{owner}", name: "{repo}") {
pullRequest(number: {pr}) {
reviewThreads(first: 50) {
nodes {
id
isResolved
comments(first: 1) {
nodes {
body
path
line
}
}
}
}
}
}
}'
4. Present unresolved comments
Summarize each comment showing:
- File path and line number
- The core issue (ignore HTML badges, buttons, metadata)
- Severity if mentioned (High/Medium/Low)
5. Verify before fixing
Read the relevant code and verify each issue is valid before fixing.
6. Fix and respond
For each valid issue:
Fix the code
Reply to the thread with Claude signature:
IMPORTANT: All responses MUST end with the Claude signature to make it clear the response was AI-generated:
🤖 _Response by [Claude Code](https://claude.com/claude-code)_
Write the response to a temp file first (to avoid heredoc issues), then post:
# Write response with signature
printf '%s\n' \
'Fixed! [explanation of what was changed]' \
'' \
'🤖 _Response by [Claude Code](https://claude.com/claude-code)_' \
> /tmp/claude/pr-comment.md
# Post the comment
gh api graphql -f query='
mutation($body: String!) {
addPullRequestReviewThreadReply(input: {
pullRequestReviewThreadId: "{thread_id}"
body: $body
}) {
comment { id }
}
}' -f body="$(cat /tmp/claude/pr-comment.md)"
- Resolve the thread:
gh api graphql -f query='
mutation {
resolveReviewThread(input: { threadId: "{thread_id}" }) {
thread { isResolved }
}
}'
- Clean up:
rm /tmp/claude/pr-comment.md
7. Commit and push
Commit all fixes with a message referencing the review feedback, then push.
Examples
User says: "Check the PR comments" Action: Fetch comments for current branch's PR, present issues, ask which to fix
User says: "Address the review feedback on PR 42" Action: Fetch comments for PR #42, fix valid issues, respond and resolve threads
User says: "Respond to the reviewers" Action: Reply to review threads explaining fixes, resolve addressed comments