fetch-pr-review-comments
MUST use this skill when user asks to check/review PR comments, address reviewer feedback, fix review issues, or respond to code review. Fetches unresolved review comments from GitHub PR for the current branch.
When & Why to Use This Skill
This Claude skill streamlines the software development lifecycle by automating the retrieval of unresolved GitHub pull request comments directly into the AI's workspace. It eliminates the need for manual context switching between the browser and the terminal, allowing developers to quickly identify, analyze, and prepare to address reviewer feedback within their coding environment.
Use Cases
- Efficient Feedback Resolution: Quickly fetch and list all pending reviewer comments on a current branch to systematically address issues without leaving the IDE.
- Pre-merge Quality Check: Verify if there are any remaining unresolved discussions or requested changes before finalizing a pull request for merge.
- Contextual Refactoring: Provide Claude with the exact text of reviewer feedback to generate targeted code fixes or architectural improvements based on specific peer suggestions.
| name | fetch-pr-review-comments |
|---|---|
| description | MUST use this skill when user asks to check/review PR comments, address reviewer feedback, fix review issues, or respond to code review. Fetches unresolved review comments from GitHub PR for the current branch. |
Fetch PR Review Comments
Fetches unresolved review comments from the GitHub pull request corresponding to the current branch. You should use the bundled script to do this.
Instructions
- Run the script:
bash ~/.claude/skills/fetch-pr-review-comments/get_unresolved_review_comments.sh - Report the fetched unresolved review comments in a clear format. Do not use table format.
- STOP HERE - Do not proceed to fix or address the comments yet.
- Wait for user to explicitly request fixes.
Important Notes
- Requires
ghCLI to be authenticated - Only works when on a branch that has an associated pull request
- After reporting the comments, STOP and WAIT for user instructions. DO NOT:
- Create todo lists for fixing the comments
- Read or edit the mentioned files
- Start implementing any fixes