Skip to content
TrustedSkillsbeta
Back to all skills

Git Branch Pr Workflow

Checked
laurigates·vlatest·backend·MIT

Automates Git branch creation, pull request generation, and basic workflow tasks based on user instructions.

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 laurigates/claude-plugins --skill git-branch-pr-workflow -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

laurigates

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 laurigates/claude-plugins at 45d1d7dcf6.

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

Commit
45d1d7dcf6
Manifest
git-plugin/skills/git-branch-pr-workflow/SKILL.md
Scanned
3 files, 617 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 git-branch-pr-workflow skill automates the creation of feature branches and Pull Requests from within a chat interface, streamlining the software delivery pipeline. It handles the entire workflow lifecycle, ensuring code changes are isolated and reviewed before merging into the main repository.

When to use it

  • You need to quickly spin up an isolated environment for a new feature or bug fix without leaving your current task context.
  • Your team requires strict code review processes where every change must be submitted as a Pull Request for approval.
  • You want to maintain a clean main branch by ensuring all development happens on dedicated, named branches.

Key capabilities

  • Automatically creates new Git branches based on user-defined naming conventions or feature descriptions.
  • Generates and submits Pull Requests with appropriate titles and descriptions directly from the conversation.
  • Integrates seamlessly with existing Git repositories to track changes without manual CLI interaction.

Example prompts

  • "Create a branch called fix-login-bug for the issue we just discussed and open a PR."
  • "Start a new feature branch for the dashboard redesign and submit it for review."
  • "Branch off main to work on the API integration endpoint and create a pull request with the details."

Tips & gotchas

Ensure your Git repository is properly configured and accessible before invoking this skill, as it relies on existing remote connections. The skill assumes standard branch naming conventions; verify that your team's specific guidelines align with the generated branch names to avoid merge conflicts or review delays.