gh-review-requests
Helps your agent find important GitHub notifications. It searches for code review requests for you or your team.
What it does
This tool fetches unread GitHub notifications where your team was asked to review code. It helps you quickly see what needs your attention.
When to use it
- ✓When you want to know which open code changes need your review.
- ✓To see review requests for a specific team.
- ✓If you want an organized list instead of searching GitHub notifications.
Example of what to ask your AI
“Show me review requests for the 'frontend' team.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool uses a program called 'gh' to connect to GitHub. It looks for pending review notifications for the team you specify and shows the code details.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill gh-review-requestsOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/gh-review-requests/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
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 a slug or display name, then resolve it against the authenticated organization's actual teams.
Step 2: Read the Actual Queue
No fetch_review_requests.py script is bundled in this AAS entrypoint. Use the
configured GitHub connector or authenticated gh API rather than inventing it.
Confirm the organization and exact team slug from its API; display-name conversion
alone cannot prove the slug. Do not default every repository to getsentry.
gh api notifications --paginate
Keep unread review_requested notifications whose subject is a pull request.
Follow the returned subject API URL only after verifying GitHub origin and repository.
For each candidate, inspect open/unmerged state, requested reviewer teams, and the
selected team's paginated membership. Being authored by a teammate is distinct from
being assigned for review. Do not mark notifications read or submit reviews.
Return the actual API results as rows with PR URL, author, and observed reason. Missing permissions or incomplete pagination must be reported as incomplete, not zero.
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."
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
FAQ
Do I need to install anything?
Yes, you need to have 'gh' (GitHub CLI) installed and authenticated with your GitHub account.
What does 'review requested' mean?
It means someone has asked you or your team to look at and provide feedback on code that is under development.
Does it mark notifications as read?
No, this tool only displays notifications; it does not mark them as read or submit reviews.
Details
Original description by the author
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".
Popularity
- GitHub stars
- 48k
- Ranking position
- #3116
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
bun-runtime
Has your agent use Bun to run, organize, and test code. It helps choose Bun over other tools and migrate existing projects.
affaan-m/ECC
database-migrations
Helps your agent make safe changes to databases. It ensures changes can be undone and minimizes downtime.
affaan-m/ECC
deployment-patterns
Sets up deployment and CI/CD workflows, containerization, and rollback strategies to ensure safe releases.
affaan-m/ECC