Get Pr Comments
- 1.4k installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
get-pr-comments is a Cursor skill that fetches and summarizes GitHub pull-request review and discussion comments into a prioritized action list for developers addressing active PR feedback.
About
get-pr-comments is a Cursor plugin skill that resolves the active pull request for the current branch, pulls GitHub review comments and discussion threads, and returns a concise, severity-grouped summary with a prioritized action list. Instead of switching between the IDE and GitHub in a browser, developers get grouped feedback, ordered next steps, and flagged open questions that still need clarification from reviewers. get-pr-comments fits the moment a feature branch is under review and scattered inline comments, approval notes, and thread replies must be triaged quickly. The workflow targets actionable remediation: critical blockers surface first, nitpicks are separated, and unresolved questions are explicit so merge readiness is clear.
- Fetches latest PR comments from GitHub into your Cursor workspace
- Summarizes reviewer feedback and action items
- Reduces context switching between browser and editor
- Supports threaded discussions and code suggestions
Get Pr Comments by the numbers
- 1,350 all-time installs (skills.sh)
- +209 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #50 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill get-pr-commentsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
How do you summarize GitHub PR review comments in Cursor?
Automatically pull and summarize PR comments from GitHub directly into Cursor so they can address feedback without switching windows.
Who is it for?
Developers on an active feature branch who need a fast, prioritized digest of GitHub PR review feedback without leaving Cursor.
Skip if: Teams not using GitHub pull requests or developers who already resolved all review threads and only need to merge.
When should I use this skill?
A pull request has fresh review comments, inline feedback, or discussion threads that need triage before the next commit.
What you get
Grouped feedback summary, priority-ordered action list, and a list of open reviewer questions.
- grouped feedback summary
- priority action list
- open questions list
Files
Get PR comments
Trigger
Need a concise, actionable summary of feedback on the active pull request.
Workflow
1. Resolve the active PR for the current branch. 2. Fetch review comments and discussion comments. 3. Group feedback by severity and actionability. 4. Return a concise action list.
Output
- Grouped feedback summary
- Action list ordered by priority
- Open questions that still need clarification
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Use get-pr-comments when you want in-IDE PR comment triage instead of manually scanning GitHub review threads in a browser.
FAQ
What does get-pr-comments return?
get-pr-comments returns a grouped feedback summary, a priority-ordered action list, and open questions that still need reviewer clarification. The skill resolves the active PR for the current branch before fetching GitHub review and discussion comments.
When should get-pr-comments run?
get-pr-comments should run when a developer needs a concise, actionable summary of feedback on the active pull request. Trigger it after new review comments land or before pushing fixes so blockers and nitpicks are triaged in Cursor.