Skills ZICQ category：Agent Workflows gh-review-requests

Gh Review Requests

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".

3760 installs

Official URL：skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

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

When to use it

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"

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: GitHub Review Requests; Step 1: Identify the Team; Step 2: Run the Script; Script output; Step 3: Present Results; Fallback. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references scripts/fetch_review_requests.py. Those resources load on demand.

GitHub Review RequestsStep 1: Identify the TeamStep 2: Run the ScriptScript outputStep 3: Present ResultsFallback

· allowed-tools：Bash

Source category：skills.sh agent-skill

Sources & links

Market sources：skills.sh

Full package on GitHub

OSS Skill ranking

SKILL.md & Agent activation

Official spec ↗

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: BashExperimental field; support depends on the client and does not grant permissions by itself.

DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.

Files referenced by the instructions · 1

scripts/fetch_review_requests.py

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "gh-review-requests" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-7134516e0bc7786c-Gh-Review-Requests.html
Save it as .cursor/skills/gh-review-requests/SKILL.md or .claude/skills/gh-review-requests/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/getsentry/skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/getsentry/skills' --list

npx skills add 'https://github.com/getsentry/skills' --skill 'gh-review-requests'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

SKILL.md source Copy freely; the source file is unchanged

# 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

```bash
uv run scripts/fetch_review_requests.py --org getsentry --teams <team-slug>
```

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

```bash
uv run scripts/fetch_review_requests.py --org getsentry --teams <team slugs>
```

### Script output

```json
{
  "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:

```bash
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

Readable layout

--- 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 ```bash uv run scripts/fetch_review_requests.py --org getsentry --teams ``` To filter by multiple teams, pass a comma-separated list: ```bash uv run scripts/fetch_review_requests.py --org getsentry --teams ``` ### Script output ```json { "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: "` — the team is a requested reviewer - `"opened by: "` — 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: ```bash 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

Related skills

Agent Workflows

Gh Review Requests

What this skill does

What it does

When to use it

How agents load it

File analysis

SKILL.md & Agent activation

Install this skill

Related skills

Skill Creator

Clawdhub

Agent Team Orchestration

Superpowers