GitHub Review Requests

VerifiedCaution

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.

Sby Skills Guide Bot
ProductivityBeginner
7/23/2026
Claude Code
#github#code-review#notifications#cli#team-workflow

Recommended for

Automated summary

Fetches unread GitHub review-requested notifications for open pull requests, filtered by team, and presents them as a markdown table.

Strengths

  • Filters review requests by GitHub team, covering both PRs where the team is a requested reviewer and those opened by a team member
  • Skips closed or merged PRs so only genuinely pending reviews remain
  • Structured JSON output with explicit reasons (review requested from / opened by)
  • Includes a manual fallback procedure using gh api if the script fails

Limitations

  • Assumes the user knows their team slug and that gh is already authenticated
  • Relies on a Python script run via uv, adding a tooling dependency
  • Limited to unread review_requested notifications, with no handling of mentions or other notification types
When to use it

When you want a quick view of which pull requests from your team are waiting on your review.

When not to use it

If you need to triage all GitHub notifications or analyze PRs that aren't tied to a specific team.

Security analysis

Caution
Quality score88/100

The skill appears to be a legitimate read-only workflow for fetching GitHub review requests. It does not instruct destructive actions, obfuscation, or secret exfiltration, but it does rely on Bash, an authenticated `gh` session, `uv run`, and network API calls, so it warrants caution rather than being treated as risk-free.

Findings
  • •Uses Bash and an authenticated GitHub CLI (`gh`) to query notifications, PRs, requested reviewers, and team membership over the network.
  • •Executes a bundled Python script via `uv run`; the script itself is not included in SKILL.md, so its exact behavior cannot be fully audited from the provided text.
  • •Fallback path performs paginated GitHub API calls and per-notification lookups, which requires broad read access to organization and repository metadata.
How this analysis is made

Examples

Find my review requests
What needs my review? Filter by the streaming-platform team.
Check team review queue
Check the review queue for opensource and platform teams in the getsentry org.
Two-team filter
Show my review requests for the getsentry org, teams ingests and ops.

name: gh-review-requests description: Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue". allowed-tools: Bash

GitHub Review Requests

Fetch unread review_requested notifications for open (unmerged) PRs, filtered by a GitHub team.

Requires: GitHub CLI (gh) authenticated.

Requires: The uv CLI for python package management, install guide at https://docs.astral.sh/uv/getting-started/installation/

Step 1: Identify the Team

If the user has not specified a team, ask:

Which GitHub team should I filter by? (e.g. streaming-platform)

Accept either a team slug (streaming-platform) or a display name ("Streaming Platform") — convert to lowercase-hyphenated slug before passing to the script.

Step 2: Run the Script

uv run ${CLAUDE_SKILL_ROOT}/scripts/fetch_review_requests.py --org getsentry --teams <team-slug>

To filter by multiple teams, pass a comma-separated list:

uv run ${CLAUDE_SKILL_ROOT}/scripts/fetch_review_requests.py --org getsentry --teams <team slugs>

Script output

{
  "total": 3,
  "prs": [
    {
      "notification_id": "12345",
      "title": "feat(kafka): add workflow to restart a broker",
      "url": "https://github.com/getsentry/ops/pull/19144",
      "repo": "getsentry/ops",
      "pr_number": 19144,
      "author": "bmckerry",
      "reasons": ["opened by: bmckerry"]
    }
  ]
}

reasons will contain one or both of:

  • "review requested from: <Team Name>" — the team is a requested reviewer
  • "opened by: <login>" — the PR author is a team member

Step 3: Present Results

Display results as a markdown table with full URLs:

| # | Title | URL | Reason | |---|-------|-----|--------| | 1 | feat(kafka): add workflow to restart a broker | https://github.com/getsentry/ops/pull/19144 | opened by: evanh |

If total is 0, say: "No unread review requests found for that team."

Fallback

If the script fails, run manually:

gh api notifications --paginate

Then for each review_requested notification, check:

  • gh api repos/{repo}/pulls/{number} — skip if state == "closed" or merged_at is set
  • gh api repos/{repo}/pulls/{number}/requested_reviewers — check teams[].name
  • gh api orgs/{org}/teams/{slug}/members — check if author is a member

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/github-review-requests-mrx3xxy0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/github-review-requests-mrx3xxy0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-review-requests-mrx3xxy0/download' --output '.skill-downloads/github-review-requests-mrx3xxy0/SKILL.md.part' && mv '.skill-downloads/github-review-requests-mrx3xxy0/SKILL.md.part' '.skill-downloads/github-review-requests-mrx3xxy0/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/github-review-requests-mrx3xxy0/SKILL.md' && test -s '.skill-downloads/github-review-requests-mrx3xxy0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gh-review-requests' && cp -R '.skill-downloads/github-review-requests-mrx3xxy0' '.claude/skills/gh-review-requests'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/github-review-requests-mrx3xxy0'

openskills read 'github-review-requests-mrx3xxy0'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/github-review-requests-mrx3xxy0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills