gh-review-requests

Pulls together the code reviews your team has been asked for, and the ones teammates have just opened, out of the pile of unread GitHub notifications.

WHEN TO USE

SCOPE

USE FOR

List the open PRs your team still needs to review, filtered by team slug or team name.
Check whether a PR notification came from a review request or just from a teammate opening it.
Fall back to raw gh api calls to find review requests when the bundled script fails.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (5)

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 scripts/fetch_review_requests.py --org getsentry --teams <team-slug>

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

uv run 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

Account or credentials required

2 FOR YOU

All items below are required.

01
Authenticate the GitHub CLI
Have gh authenticated so it can read notifications, pull requests, and team membership through the GitHub API.
02
Install the uv Python package manager
Install uv (docs.astral.sh/uv) so the bundled scripts/fetch_review_requests.py script can run.

Listed as free: Connected services may require an account or charge fees.

This skill ships inside the Sentry Engineering Skills plugin. Listed package contents include 2 agents. Installed components and skill versions may vary by AI tool.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add getsentry/skills --skill "gh-review-requests" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Sentry Engineering Skills plugin package selected for your AI tool.

Claude Code

Add Sentry's marketplace, then install the plugin

Run both lines in a terminal. The first adds Sentry's marketplace, which is this repository; the second installs the sentry-skills plugin, which Sentry describes as agent skills for its employees, plus two subagents. It installs for you in every project; restart Claude Code afterwards, as Sentry's README says.

claude plugin marketplace add getsentry/skills

claude plugin install sentry-skills@sentry-skills

Open plugin page ↗

What's inside

Files included with this skill.

View on GitHub