gh-get-review-comments
Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR.
When & Why to Use This Skill
This Claude skill enables seamless retrieval of all review comments from GitHub pull requests using the GitHub API. It streamlines the code review process by allowing developers to quickly access, filter, and analyze feedback directly within their AI-powered workflow, ensuring no critical suggestions are missed during the development cycle.
Use Cases
- Audit Unresolved Feedback: Quickly identify and list all comments that haven't been addressed to ensure code quality before merging.
- Reviewer Analysis: Filter comments by specific reviewers to understand different perspectives and prioritize feedback from lead engineers.
- Automated Feedback Summarization: Use the retrieved comment data to generate a high-level summary of requested changes for project managers or team leads.
- Contextual Debugging: Locate specific file paths and line numbers associated with review comments to jump directly to the code requiring fixes.
| name | gh-get-review-comments |
|---|---|
| description | "Retrieve all review comments from a pull request using the GitHub API. Use when you need to see what feedback has been provided on a PR." |
| category | github |
Get PR Review Comments
Retrieve and analyze all review comments from a pull request.
When to Use
- Checking for unresolved review feedback
- Analyzing reviewer feedback before fixing
- Verifying all comments have been addressed
- Getting comment IDs for replies
Quick Reference
# Get all review comments
gh api repos/OWNER/REPO/pulls/PR/comments
# Get comments with formatting
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | {id: .id, path: .path, body: .body}'
# Filter by reviewer
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | select(.user.login == "username")'
# Get only unresolved comments
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | select(.in_reply_to_id == null)'
Workflow
- Fetch comments: Use API to list all comments
- Parse output: Extract IDs and feedback
- Analyze feedback: Understand what needs fixing
- Plan fixes: Decide how to address each comment
- Apply fixes: Make the requested changes
Output Format
Comments include:
id- Comment ID (use for replies)path- File where comment was madeline- Line number of commentbody- Comment textuser- Reviewer usernamein_reply_to_id- Parent comment ID (null if top-level)
Error Handling
| Problem | Solution |
|---|---|
| PR not found | Verify PR number |
| Auth failure | Check gh auth status |
| No comments | API returns empty array (not an error) |
| Permission denied | Check authentication scopes |
Filtering Examples
Comments on specific file:
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | select(.path == "src/file.mojo")'
Comments by specific reviewer:
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | select(.user.login == "reviewer")'
Only top-level comments (not replies):
gh api repos/OWNER/REPO/pulls/PR/comments \
--jq '.[] | select(.in_reply_to_id == null)'
References
- See gh-reply-review-comment skill for replying to comments
- See gh-fix-pr-feedback skill for workflow to address feedback
- GitHub API docs: https://docs.github.com/en/rest/pulls/comments