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".
Security Assessment
About gh-review-requests
The 'gh-review-requests' skill is designed to streamline the process of monitoring GitHub pull requests that require attention from a user or their team. It fetches unread notifications for open PRs where a review has been requested either from a specified team or authored by a team member. By focusing on 'review_requested' notifications, it eliminates the need to manually scan through all GitHub activity, helping users quickly identify which PRs need their input and ensuring timely code reviews across their organization.
This skill leverages the GitHub CLI ('gh') and the 'uv' CLI for Python package management to run a script that filters notifications by organization and team. Users can specify a single team or multiple teams to narrow down results. The script outputs structured JSON containing the total number of relevant PRs and detailed information for each, including PR title, URL, repository, author, and reason for inclusion. Reasons indicate whether the PR was opened by a team member or if a team review was requested. Results are then presented as a markdown table for easy readability. If the automated script fails, a manual fallback using 'gh api' commands is available to perform the same filtering process.
Ideal use cases include developers, team leads, or code reviewers who need a consolidated view of pending PRs that require attention. It is especially useful in large organizations with multiple teams, ensuring that review requests do not go unnoticed. Target users are those familiar with GitHub and CLI operations, seeking efficiency in code review management, team collaboration, and workflow organization.
FAQ
How do I specify which team to filter review requests by?
You can provide either a team slug (e.g., 'streaming-platform') or a display name (e.g., 'Streaming Platform'). The skill converts display names to lowercase hyphenated slugs for the script.
What are the requirements to run this skill?
You need an authenticated GitHub CLI ('gh') and the 'uv' CLI for Python package management installed. Installation instructions for 'uv' are available at https://docs.astral.sh/uv/getting-started/installation/.
Can I filter review requests for multiple teams at once?
Yes, you can pass a comma-separated list of team slugs to the script to fetch PRs for multiple teams simultaneously.
What happens if there are no unread review requests?
If the total number of relevant PRs is zero, the skill will indicate: 'No unread review requests found for that team.'
Is there a fallback if the automated script fails?
Yes, you can manually use 'gh api notifications' and additional 'gh api' commands to filter 'review_requested' notifications and verify PR states and team membership.
Install gh-review-requests
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
getsentry/skills