get-pr-comments

Fetch and summarize review comments from the active pull request.

3|Updated Apr 8, 2025

Search Tags:#git #code review #pull request #github #review comments #feedback summary

One-click install

npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill get-pr-comments-zanzythebar

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: get-pr-comments
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/get-pr-comments
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill get-pr-comments-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull request feedback scattered across review comments and discussion threads is time-consuming, and it is easy to miss actionable items buried in long conversations. ## Core Features & Use Cases - Automatic PR Resolution: Identifies the active pull request for the current branch without manual lookup. - Grouped Feedback Summary: Collects review and discussion comments, then groups them by severity and actionability. - Prioritized Action List: Returns an ordered list of changes to make plus open questions needing clarification. - Use Case: After pushing changes to a feature branch, ask for a summary of reviewer feedback to quickly plan your next round of fixes before re-requesting review. ## Quick Start Ask the assistant to summarize the review comments on the pull request for my current branch.

Frequently Asked Questions about get-pr-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I get a summary of pull request review comments?▼

Invoke this skill on a branch with an open pull request. It resolves the active PR, fetches review and discussion comments, and returns feedback grouped by severity with a prioritized action list.

How to prioritize PR feedback before addressing reviewer comments?▼

The skill groups feedback by severity and actionability, then outputs an ordered action list. Items needing clarification are surfaced separately as open questions so you can resolve blockers first.

Does this work if my branch has no open pull request?▼

No. The workflow's first step is resolving the active PR for the current branch, so an open pull request must exist. Create the PR first, then run the summary.

What types of pull request comments are included in the summary?▼

Both inline review comments and general discussion comments on the pull request are fetched. They are then grouped by severity and actionability into a concise summary.