Skip to content
TrustedSkillsbeta
Back to all skills

Gh Review Requests

Official
getsentry·vlatest·backend·Apache-2.0

Automatically reviews GitHub pull requests, flagging potential issues based on Sentry's error monitoring data and best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add getsentry/skills --skill gh-review-requests -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

getsentry

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: api.github.com, github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.github.comsource hostgithub.comsource host

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned getsentry/skills at c2f99a5b04.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c2f99a5b04
Manifest
skills/gh-review-requests/SKILL.md
Scanned
2 files, 186 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to interact with GitHub's review request workflow, allowing them to identify who needs to review a pull request and manage those requests directly within the platform. It streamlines the code approval process by automating the discovery of assignees for specific changes.

When to use it

  • An agent needs to automatically find the appropriate maintainers or reviewers for a newly created pull request based on file paths or repository rules.
  • A workflow requires notifying specific team members when their assigned review tasks are pending or overdue.
  • You want an agent to update the list of requested reviewers after a change in project ownership or team structure.

Key capabilities

  • Identifies required reviewers for open pull requests.
  • Manages GitHub review request assignments programmatically.
  • Integrates directly with the GitHub API for real-time status updates.

Example prompts

  • "Find all open pull requests in this repository that are missing a reviewer and assign them to the 'backend' team."
  • "Who is currently requested to review PR #402, and has their review been approved yet?"
  • "Update the review request for the latest feature branch to include @senior-dev and remove @intern-user."

Tips & gotchas

Ensure your AI agent has valid GitHub API credentials with repo scope permissions, as managing review requests requires write access to pull requests. This skill relies on the current state of the repository; if a PR is merged or closed, the agent must be instructed to handle that lifecycle event separately.