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".
About this skill
This AI agent skill, `gh-review-requests`, empowers your agent to efficiently manage and track GitHub code review queues. It directly queries GitHub to fetch unread notifications specifically for open Pull Requests where a review has been requested from a designated GitHub team or opened by a team member. Leveraging the GitHub CLI (`gh`), it provides real-time, accurate information, allowing developers and team leads to quickly identify and address pending reviews. Part of the "antigravity-awesome-skills" collection, it integrates seamlessly to enhance an AI agent's capability in developer workflows.
Best use case
Developers and team leads needing to quickly find open Pull Requests that require their attention or the attention of their team for review, ensuring timely feedback and preventing bottlenecks in the development pipeline.
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".
A structured list of unread GitHub notifications for open Pull Requests, filtered by the specified team, where a review is requested. Each item typically includes the repository, PR title, and a direct link to the Pull Request.
Practical example
Example input
Hey AI, can you show me the GitHub PRs that the 'frontend-devs' team needs to review?
Example output
Certainly! I found these unread review requests for the 'frontend-devs' team: * `my-org/web-app-repo` - PR #101: Implement dark mode toggle (review requested by @jane_doe) * `my-org/design-system` - PR #25: Update button component styles (review requested by @john_smith) You can click the links above to view them on GitHub.
When to use this skill
- Use this skill when you need to know "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue". It's particularly useful when you want to filter these requests by a specific GitHub team.
When not to use this skill
- Do not use this skill if you are looking for all GitHub notifications (not just review requests), notifications for merged Pull Requests, or if the GitHub CLI (`gh`) is not installed and authenticated in the agent's environment. It's also not suitable for creating PRs or managing other GitHub features like issues.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gh-review-requests/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gh-review-requests Compares
| Feature / Agent | gh-review-requests | Standard Approach |
|---|---|---|
| Platform Support | Claude | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | medium | N/A |
Frequently Asked Questions
What does this skill do?
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".
Which AI agents support this skill?
This skill is designed for Claude.
How difficult is it to install?
The installation complexity is rated as medium. You can find the installation instructions above.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# GitHub Review Requests
Fetch unread `review_requested` notifications for open (unmerged) PRs, filtered by a GitHub team.
**Requires**: GitHub CLI (`gh`) authenticated.
## When to Use
- You need to find unread GitHub PR review requests for a specific team.
- You want to check which open PRs currently need your review or a teammate's review.
- You need a filtered review queue instead of manually browsing GitHub notifications.
## 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 ${CLAUDE_SKILL_ROOT}/scripts/fetch_review_requests.py --org getsentry --teams <team-slug>
```
To filter by multiple teams, pass a comma-separated list:
```bash
uv run ${CLAUDE_SKILL_ROOT}/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 memberRelated Skills
code-reviewer
Elite code review expert specializing in modern AI-powered code
n8n-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
mermaid-expert
Create Mermaid diagrams for flowcharts, sequences, ERDs, and architectures. Masters syntax for all diagram types and styling.
mcp-builder-ms
Use this skill when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
makepad-deployment
CRITICAL: Use for Makepad packaging and deployment. Triggers on: deploy, package, APK, IPA, 打包, 部署, cargo-packager, cargo-makepad, WASM, Android, iOS, distribution, installer, .deb, .dmg, .nsis, GitHub Actions, CI, action, marketplace
macos-menubar-tuist-app
Build, refactor, or review SwiftUI macOS menubar apps that use Tuist.
kaizen
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
issues
Interact with GitHub issues - create, list, and view issues.
hugging-face-tool-builder
Your purpose is now is to create reusable command line scripts and utilities for using the Hugging Face API, allowing chaining, piping and intermediate processing where helpful. You can access the API directly, as well as use the hf command line tool.
git-pushing
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.
git-hooks-automation
Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI.
fp-types-ref
Quick reference for fp-ts types. Use when user asks which type to use, needs Option/Either/Task decision help, or wants fp-ts imports.