Skip to content
TrustedSkillsbeta
Back to all skills

Pull Requests

Checked
coder·vlatest·backend·AGPL-3.0

This skill automatically generates pull request descriptions based on code changes, saving developers time and ensuring consistent documentation.

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 coder/xum --skill pull-requests --full-depth -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

coder

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 coder/mux at 54082e00e3.

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

Scanned
1 file, 150 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 allows AI agents to interact with and manage pull requests on code repositories. It can be used to review changes, merge or reject PRs, and provide feedback to contributors. The agent can automate parts of the pull request workflow, streamlining development processes.

When to use it

  • Code Review Automation: Automatically analyze new pull requests for potential issues based on defined criteria.
  • Merge Request Management: Assist in merging approved pull requests or flagging those requiring further attention.
  • Contributor Feedback: Provide automated feedback to developers submitting pull requests, ensuring code quality and adherence to standards.
  • Release Preparation: Help prepare a release by reviewing and organizing pending pull requests.

Key capabilities

  • Pull request review
  • Merge/Reject PRs
  • Automated feedback generation

Example prompts

  • "Review the latest pull request for feature X."
  • "Can you merge this pull request if all tests pass?"
  • "Provide feedback on the changes in this pull request, focusing on code style."

Tips & gotchas

This skill requires access to a code repository (e.g., GitHub, GitLab) and appropriate permissions to interact with pull requests. Ensure the agent is properly authenticated before use.