Skip to content
TrustedSkillsbeta
Back to all skills

Create Pr

Checked
cartridge-gg·vlatest·backend

Generates pull requests on cartridge-gg repositories based on provided specifications and code changes.

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 cartridge-gg/controller --skill create-pr -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

cartridge-gg

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 cartridge-gg/controller at b282b7b18d.

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

Commit
b282b7b18d
Manifest
.agents/skills/create-pr/SKILL.md
Scanned
4 files, 528 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 automates the creation of pull requests (PRs) on GitHub. It can generate PR titles and descriptions based on provided context, streamlining the code review process. The tool simplifies collaboration by automatically creating a draft PR for review.

When to use it

  • You've made changes in a development branch and want to quickly create a PR for review without manual steps.
  • You need to automate the creation of PRs based on specific events or triggers within your workflow.
  • You want to ensure consistent formatting and content for PR titles and descriptions across your team.
  • You're working with multiple contributors and want to facilitate efficient code reviews.

Key capabilities

  • Automated pull request generation
  • Draft PR creation
  • PR title and description generation based on context

Example prompts

  • "Create a draft PR for the changes in branch 'feature/new-login'."
  • "Generate a PR with the title 'Fix: Issue #123 - Incorrect calculation' and a description summarizing the fix."
  • "Create a pull request from my current branch, pre-filled with a descriptive title."

Tips & gotchas

  • Ensure you have appropriate permissions to create branches and pull requests in the target repository.
  • The quality of the PR title and description depends on the clarity and completeness of the provided context.