skills.rest
Kevin-Liu-01
Kevin-Liu-01COMMUNITY
Explore all skills by this author →
Website𝕏@kevskgsGitHub

pr-review

Fetch and classify GitHub PR comments into blocking and non-blocking summaries.

16|3|Updated May 5, 2026
Search Tags:#automation#github#review#pr#triage#pull-request
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill pr-review-kevin-liu-01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/pr-review
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill pr-review-kevin-liu-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triaging PR feedback can be time-consuming and error-prone. This skill automates the collection and classification of all PR comments to surface the highest-priority items for action.

Core Features & Use Cases

  • Fetch all PR feedback: Retrieve inline review comments and issue-level discussions for a given PR.
  • Classify & prioritize: Label comments as blocking vs non-blocking based on review.md prefixes and include file:line context when available.
  • Actionable summaries: Produce a structured summary with recommended next steps for blockers and a digest for non-blockers, suitable for syncs or ticketing.

Quick Start

Provide a PR number to triage, and the skill will fetch comments, classify them, and return a structured summary.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I triage pull request feedback automatically on GitHub?▼

Pull request triage can be automated by fetching both inline review comments and issue-level comments from a GitHub PR. The system classifies each comment by author, type, file:line, and body to determine blocking status, then outputs a structured summary with actionable next steps.

What is the best way to classify blocking versus non-blocking PR comments?▼

Blocking versus non-blocking PR comments are classified using review.md prefix semantics. The system evaluates the body of each inline review comment and issue-level discussion to separate blockers from non-blockers, generating a digest for the latter.

Does this PR triage tool require any specific GitHub permissions or dependencies?▼

No specific dependencies are required to use this PR triage tool. You simply provide a GitHub PR number, and the skill fetches the inline and issue-level comments, classifies them, and returns the structured summary without needing additional components.

How do I get a structured summary of GitHub PR reviews for a ticketing system?▼

To get a structured summary of GitHub PR reviews for a ticketing system, provide a PR number. The skill outputs recommended next steps for blocking items and a digest for non-blocking items, making the result suitable for syncs or ticketing.

Can I extract file and line number context from GitHub inline review comments?▼

You can extract file and line number context from GitHub inline review comments during the classification process. The triage output includes file:line context when available, alongside the author, type, and body of each comment.

Related Skills

Explore More Software Engineering Skills→
acatlacatl
1

triage-pr-comments

Triage PR review comments into prioritized verdicts and action plans.

Community
Advanced
drunkcodingdrunkcoding
4

meeting-summary

Convert raw meeting notes into structured Markdown summaries with decisions and action items.

Community
Advanced
joelhooksjoelhooks
729

pr-triage

Fetch PR comment metadata first and expand bodies on demand.

Community
Advanced
marcuskroghmarcuskrogh

review-fix

Automate iterative code review and fix-forward workflows on GitHub branches.

Community
Advanced