Skip to content
TrustedSkillsbeta
Back to all skills

Create Pull Request

Checked
cline·vlatest·backend·Apache-2.0

Automatically generates and opens GitHub pull requests based on your defined changes and branch specifications.

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 cline/cline --skill create-pull-request -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

cline

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 cline/cline at 9aa81e81e6.

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

Commit
9aa81e81e6
Manifest
.agents/skills/create-pull-request/SKILL.md
Scanned
1 file, 181 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

The create-pull-request skill enables AI agents to automatically generate and submit pull requests directly within a repository. It streamlines the contribution workflow by handling code changes, commit messages, and PR metadata without manual intervention.

When to use it

  • Automating bug fixes identified during automated testing or security scans.
  • Submitting feature implementations after an agent completes coding tasks.
  • Creating documentation updates based on new code additions or refactoring.
  • Generating PRs for dependency upgrades or configuration changes.

Key capabilities

  • Drafts pull requests with appropriate titles and descriptions.
  • Assigns relevant reviewers if configured in the environment.
  • Sets target branches accurately based on repository structure.
  • Includes commit history context in the PR body.

Example prompts

"Create a pull request for the new authentication module I just added to the src/auth directory." "Generate a pull request to fix the null pointer exception in the payment service, targeting the develop branch." "Submit a pull request with updated API documentation reflecting the latest endpoint changes."

Tips & gotchas

Ensure the AI agent has write permissions to the target repository and access to the correct branch. Always review generated PR descriptions for accuracy before merging, as agents may misinterpret complex code logic or miss edge cases in commit summaries.