Skip to content
TrustedSkillsbeta
Back to all skills

Create Pr

Official
n8n-io·vlatest·backend

Automatically generates and submits pull requests to your Git repository based on defined workflows.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it n8n:create-pr, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add n8n-io/n8n --skill n8n: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

n8n-io

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

    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 n8n-io/n8n at 9f5c752cd1.

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

Commit
9f5c752cd1
Manifest
.agents/skills/create-pr/SKILL.md
Scanned
1 file, 182 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 create-pr skill automates the process of creating a pull request (PR) in version control systems like GitHub or GitLab. It can generate PRs based on specific branch names, commit messages, and descriptions, streamlining workflows for developers and DevOps teams.

When to use it

  • Automate repetitive PR creation tasks after code reviews or testing cycles.
  • Integrate into CI/CD pipelines to trigger PRs upon successful test runs.
  • Use in collaboration workflows where multiple contributors need to submit changes systematically.
  • Create PRs programmatically for feature branches based on predefined naming conventions.

Key capabilities

  • Creates pull requests with customizable titles and descriptions.
  • Supports integration with GitHub and GitLab APIs.
  • Can be triggered via command-line interface or workflow automation tools.
  • Accepts branch names, commit hashes, and target repositories as inputs.

Example prompts

  • "Create a PR from the feature/auth branch to main with the title 'Add user authentication'."
  • "Generate a pull request for the fix/bug123 branch using the latest commit hash."
  • "Submit a PR to the develop branch with the message 'Update dependencies and fix linting errors.'"

Tips & gotchas

  • Ensure that your environment has access to the required Git platform API tokens.
  • Verify that the target repository exists and that you have write permissions for creating PRs.