gh-review-requests

Fetches GitHub review notifications for open PRs filtered by team or author.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/promptlylabs/skills --skill gh-review-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-review-requests
Source: https://github.com/promptlylabs/skills/tree/main/plugins/promptly-skills/skills/gh-review-requests
Command: npx skills add https://github.com/promptlylabs/skills --skill gh-review-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Fetch unread review_requested notifications for open PRs filtered by a GitHub team. It helps engineers quickly identify PRs requiring review from a team or awaiting review from a specific author.

Core Features & Use Cases

  • Filter by team slug or display name, resolve names, and fetch unread review requests.
  • Validate PR state (open, not merged) and skip closed/merged PRs.
  • Output a structured summary including title, URL, repo, PR number, author, and reasons to expedite review.

Quick Start

Run the script to fetch unread PR review requests for a specified team.

Frequently Asked Questions about gh-review-requests

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

FAQPage Schema
How do I track unread GitHub pull request review requests for my team?

To track unread GitHub pull request review requests, this Skill fetches unread notifications for open PRs and filters them by specified team slugs. It outputs a structured summary with title, URL, repo, author, and reasons to expedite reviews.

Can I filter GitHub review notifications by team slug?

Yes, you can filter GitHub review notifications by team slug or display name. The Skill uses the GitHub CLI to resolve team memberships and surface only unread review requests assigned to that specific team.

Does this skip closed or merged pull requests when fetching review requests?

Yes, fetching review requests validates the PR state to ensure it is open and not merged. It automatically skips closed or merged pull requests so your team only sees items requiring current attention.

What information is included in the pull request review summary?

The pull request review summary includes structured fields such as the PR title, URL, repo, pr_number, author, and reasons. This URL-rich summary helps engineers quickly identify and access PRs requiring action.

Do I need the GitHub CLI to surface unread PR review requests?

Yes, you need the GitHub CLI to surface unread PR review requests. The Skill relies on the GitHub CLI to resolve team memberships, validate PR states, and fetch the unread notifications for open pull requests.

What is the best way to manage a team's GitHub PR review queue?

The best way to manage a team's GitHub PR review queue is filtering unread review requests by team slug. This approach surfaces only open, unmerged PRs needing attention, providing a concise summary to streamline team workflows.