Skip to content
TrustedSkillsbeta
Back to all skills

Git Branch Naming

Checked
laurigates·vlatest·backend·MIT

Generates clear, concise, and consistent Git branch names based on provided task descriptions and project conventions.

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-naming -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-naming/SKILL.md
Scanned
1 file, 242 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 enforces consistent naming conventions for Git branches, automatically generating descriptive names that reflect the feature, bug fix, or task being addressed. It streamlines repository hygiene by ensuring every new branch follows a standardized format before creation.

When to use it

  • You need to maintain a clean, predictable branch structure across a large team.
  • You want to automate the tedious process of crafting meaningful commit messages and branch names.
  • Your organization requires strict adherence to specific naming patterns (e.g., feature/, fix/, hotfix/).
  • You are setting up a new repository or refactoring an existing one to improve collaboration efficiency.

Key capabilities

  • Automatically generates branch names based on user input or context.
  • Enforces predefined naming schemas to ensure consistency.
  • Integrates directly into the Git workflow to prevent invalid branches from being created.

Example prompts

  • "Create a new branch named feature/user-authentication for the login module."
  • "Generate a branch name for fixing the critical payment gateway timeout issue."
  • "List all branches that do not follow our standard naming convention."

Tips & gotchas

Ensure your team agrees on the specific naming schema before relying on this skill, as it strictly enforces the defined rules. If you frequently work with complex projects, consider combining this with other Git skills to automate merging and conflict resolution.