gh-summarize-pr-review

Summarize GitHub pull request review feedback into an evidence-backed digest.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill gh-summarize-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-summarize-pr-review
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/gh-summarize-pr-review
Command: npx skills add https://github.com/haryelramalho/skills --skill gh-summarize-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill turns scattered GitHub pull request feedback into a structured, decision-ready brief so reviewers and authors can quickly understand what matters, why it matters, and what evidence supports each concern.

Core Features & Use Cases

  • Evidence-rich review digests: Collects inline review comments, review bodies, and issue comments into one organized summary.
  • Decision support: Classifies each point by impact so teams can separate blockers from important follow-ups and optional suggestions.
  • Traceable context: Preserves direct quotes, code snippets, source links, and referenced images to keep every review point grounded in evidence.
  • Use case: A developer wants to prepare for a merge decision, brief a teammate, or quickly review the key concerns raised on an active pull request.

Quick Start

Use this skill to summarize the current pull request review into a numbered, evidence-backed markdown report.

Frequently Asked Questions about gh-summarize-pr-review

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

FAQPage Schema
How do I summarize GitHub pull request review feedback into a single report?

To summarize GitHub pull request review feedback, this Skill collects inline comments, review bodies, and issue comments into a structured markdown digest. It preserves direct quotes, code snippets, and source links to provide an evidence-backed summary for merge decisions.

What is the best way to extract evidence from GitHub PR review comments for a merge decision?

The best way to extract evidence from GitHub PR review comments is to classify each point by decision impact. This Skill separates blockers from optional suggestions while preserving referenced images and code context to ground every review concern in traceable evidence.

Does generating a PR review summary require GitHub CLI authentication?

Yes, generating a PR review summary requires GitHub CLI authentication and a local git repository context. The Skill uses the gh CLI to access open pull requests on the current branch and extract feedback from inline comments and review bodies.

Can I collect inline code review comments and issue comments together for an active pull request?

Yes, you can collect inline code review comments and issue comments together for an active pull request. The Skill aggregates feedback from multiple GitHub sources into one organized summary, classifying each point by impact to help teams quickly review key concerns.

How does decision-impact classification work for pull request feedback digests?

Decision-impact classification for pull request feedback digests works by categorizing each extracted review point by its severity. This Skill separates blockers from important follow-ups and optional suggestions, allowing reviewers and authors to quickly understand what matters and why.

What are the limitations of summarizing PR feedback from the current git branch?

A key limitation is that this PR feedback summarization applies only to open pull requests on the current git branch. It requires a local git repository context and valid gh authentication to extract and classify the review evidence.