gh-review-requests

Name: gh-review-requests
Availability: InStock
Author: yanochka11

Fetch unread GitHub review notifications and filter pending pull requests by team.

Updated May 5, 2026

Search Tags:#code review #github #pull requests #gh cli #team workflow #review queue

Ready to run

npx skills add https://github.com/yanochka11/harness_bro --skill gh-review-requests-yanochka11

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-review-requests
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/ported/gh-review-requests
Command: npx skills add https://github.com/yanochka11/harness_bro --skill gh-review-requests-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers identify pending GitHub pull request review requests without manually searching notifications, repositories, or team activity.

Core Features & Use Cases

Review Queue Discovery: Fetch unread GitHub review-requested notifications and filter them by organization team membership or requested reviewer teams.
Automated PR Validation: Check pull request status, skip closed or merged PRs, and provide structured review information.
Use Case: A developer can quickly discover all open pull requests requiring their team's review and receive a concise list with titles, URLs, and reasons for inclusion.

Quick Start

Ask the skill to show your GitHub review requests for a specific team and provide the pending pull requests.

Frequently Asked Questions about gh-review-requests

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

FAQPage Schema

How do I find pending GitHub pull request review requests for my team?▼

To find pending GitHub pull request review requests, you can filter unread GitHub review-requested notifications by organization team membership. This fetches open pull requests requiring your team's review and provides a concise list with titles, URLs, and inclusion reasons.

Does finding GitHub review requests require authenticated CLI access?▼

Yes, finding GitHub review requests requires authenticated GitHub CLI access and the uv tool. These dependencies are necessary to execute the review request retrieval script and apply team-based filtering to your unread notifications.

Can I skip closed or merged pull requests when checking my GitHub review queue?▼

Yes, automated PR validation checks pull request status and skips closed or merged pull requests when checking your GitHub review queue. It provides structured review information only for open pull requests requiring action.

What is the best way to triage GitHub code review queues for a specific team?▼

The best way to triage GitHub code review queues is to fetch unread review-requested notifications and filter them by requested reviewer teams. This identifies relevant team-based review tasks and skips closed or merged pull requests automatically.

What limitations exist when filtering GitHub PR review requests by team?▼

Filtering GitHub PR review requests by team relies on unread notification data and team membership checks. It skips closed or merged PRs, meaning any review requests buried in read notifications or outside your configured team scope will not appear.