github-pr-comments

Fetch GitHub PR review threads and classify them by status and reviewer type.

1|Updated Jun 10, 2025
One-click install
npx skills add https://github.com/Columbia-Cloudworks-LLC/EquipQR --skill github-pr-comments-columbia-cloudworks-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-comments
Source: https://github.com/Columbia-Cloudworks-LLC/EquipQR/tree/main/.cursor/skills/github-pr-comments
Command: npx skills add https://github.com/Columbia-Cloudworks-LLC/EquipQR --skill github-pr-comments-columbia-cloudworks-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

GitHub PR review threads can be lengthy and hard to triage. This Skill fetches, categorizes, and guides resolution of PR review comments to streamline the feedback loop.

Core Features & Use Cases

  • Retrieve and normalize PR review threads, including isResolved and isOutdated flags, to surface actionable items.
  • Distinguish human reviewers, Copilot/AI reviewers, and code scanning alerts, and categorize threads accordingly.
  • Provide a structured, guided workflow for triaging, addressing, and closing review feedback in a PR.

Quick Start

Fetch the review threads for a given PR in a repository, categorize them by status, and generate a summary with remediation guidance.

Frequently Asked Questions about github-pr-comments

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

FAQPage Schema
How do I categorize GitHub PR review threads by resolved, outdated, and unresolved status?

To categorize GitHub PR review threads, fetch the target repository's PR and extract review threads to classify them into unresolved, outdated, and resolved statuses, distinguishing between human reviewers, Copilot/AI reviewers, and code scanning alerts.

What is the best way to summarize GitHub PR comments to accelerate code fixes?

The best way to summarize GitHub PR comments is to normalize review threads, including isResolved and isOutdated flags, to surface actionable items and generate remediation guidance aligned with structured triage workflows.

Can I distinguish between human reviewer feedback and Copilot AI reviews in a GitHub PR?

Yes, you can distinguish human reviewers, Copilot/AI reviewers, and code scanning alerts by fetching and categorizing PR review threads, allowing you to separate automated feedback from manual code review comments.

How do I triage lengthy GitHub PR review threads to streamline the feedback loop?

To triage lengthy GitHub PR review threads, retrieve and normalize the comments, classify them by status, and follow a structured workflow to address and close review feedback efficiently.

Does this PR review summarization approach work with code scanning alerts on GitHub?

Yes, this approach works with code scanning alerts by fetching and categorizing them alongside human and AI reviewer threads, integrating automated security or quality alerts into the structured PR review summary.

Why are GitHub PR review threads hard to triage and how can I generate remediation guidance?

GitHub PR review threads are hard to triage due to their length and mixed feedback sources. You can generate remediation guidance by categorizing threads by resolution status and reviewer type to produce a structured summary.