Skip to content
TrustedSkillsbeta
Back to all skills

Gh Pr Check

Checked
akiojin·vlatest·backend·MIT

This skill automatically checks if a pull request contains a GitHub issue reference, ensuring proper context and linking.

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 akiojin/skills --skill gh-pr-check -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

akiojin

Taken from the source listing. We haven't verified who controls this account.

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

    Makes no network calls.

    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.

  • 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 akiojin/skills at 4f72afeb9e.

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

Commit
4f72afeb9e
Manifest
github/skills/gh-pr-check/SKILL.md
Scanned
1 file, 304 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

The gh-pr-check skill allows AI agents to check a GitHub pull request's status and associated checks. It can determine if the pull request is ready for merging based on the results of configured workflows, providing valuable feedback during development cycles. The agent can also retrieve specific details about the checks, such as their names and statuses.

When to use it

  • Automated Pull Request Review: Use this skill when you need an AI agent to automatically assess a pull request's readiness for merging based on workflow check results.
  • CI/CD Pipeline Integration: Integrate with your CI/CD pipeline to provide real-time feedback on build and test statuses within pull requests.
  • Developer Assistance: Allow developers to quickly query the status of their pull requests without manually navigating GitHub.
  • Monitoring Pull Request Health: Track the overall health of a repository by monitoring the success rates of checks associated with open pull requests.

Key capabilities

  • Retrieves pull request status (ready, pending, failed).
  • Fetches check names and statuses.
  • Determines merge readiness based on workflow results.

Example prompts

  • "Check the status of pull request #123 in repository 'my-org/my-repo'."
  • "What are the current checks running on pull request #456?"
  • "Is pull request #789 ready to be merged based on its workflow check results?"

Tips & gotchas

The skill requires access to a GitHub API token with sufficient permissions to view pull requests and associated workflows. Ensure the agent has this token configured correctly for proper functionality.