How do I install the Git Branch Format skill?

Run npx skillmds@latest add somnio-software/git-branch-format in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Branch Format safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Branch Format?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Branch Format free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Branch Format?

somnio-software (@somnio-software) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Branch Format by somnio-software

Name: Git Branch Format
Author: somnio-software

Git Branch Format

Generates properly formatted Git branch names following project conventions. Use this skill whenever the user wants to name a branch, create a branch, or asks things like "what should I call this branch?", "what branch name should I use?", "help me with the branch name", or describes a feature/fix and needs a branch name. Always use this skill when the user needs a git branch name, even if they don't explicitly say "branch".

File contents

Git Branch Format Skill

Generates a branch name from a description of changes.

Convention

With ticket number

{type}/{TICKET_NUMBER}_{short_description}

TICKET_NUMBER is uppercase as provided by the user (e.g. PROJ-548)
short_description is snake_case, max 3 words — prefer 1–2
Example: feat/TICKET-548_flutter_upgrade

Without ticket number

{type}/{short_description}

short_description is snake_case, max 3 words — prefer 1–2
Example: feat/flutter_upgrade

Never use placeholders like NO-TICKET. If there's no ticket, just omit that part entirely.

Type Selection Guide

Type	When to use
`feat`	New functionality
`fix`	Bug fix
`refactor`	Code change with no behavior change
`chore`	Config, deps, tooling, maintenance
`test`	Adding or updating tests
`docs`	Documentation only
`style`	Formatting, whitespace
`perf`	Performance improvement
`ci`	CI/CD changes
`build`	Build system changes
`revert`	Reverting a previous commit

Workflow

Read the user's description of changes.
Ask: "Do you have a ticket number for this?" — if the user doesn't provide one, proceed without it.
Infer the correct type from the nature of the changes.
Generate the branch name following the convention above.

Examples

User: "I'm adding dark mode support" — Ticket: PROJ-312

feat/PROJ-312_dark_mode_support

User: "fixing a crash on the payment screen" — No ticket

fix/payment_screen_crash

User: "upgrading Flutter and fixing deprecated APIs" — Ticket: PROJ-548

feat/PROJ-548_flutter_upgrade

---name: git-branch-formatdescription: Generates properly formatted Git branch names following project conventions. Use this skill whenever the user wants to name a branch, create a branch, or asks things like "what should I call this branch?", "what branch name should I use?", "help me with the branch name", or describes a feature/fix and needs a branch name. Always use this skill when the user needs a git branch name, even if they don't explicitly say "branch".---# Git Branch Format SkillGenerates a **branch name** from a description of changes.---## Convention### With ticket number```{type}/{TICKET_NUMBER}_{short_description}```- `TICKET_NUMBER` is uppercase as provided by the user (e.g. `PROJ-548`)- `short_description` is `snake_case`, max 3 words — prefer 1–2- Example: `feat/TICKET-548_flutter_upgrade`### Without ticket number```{type}/{short_description}```- `short_description` is `snake_case`, max 3 words — prefer 1–2- Example: `feat/flutter_upgrade`Never use placeholders like `NO-TICKET`. If there's no ticket, just omit that part entirely.---## Type Selection Guide| Type | When to use ||------|-------------|| `feat` | New functionality || `fix` | Bug fix || `refactor` | Code change with no behavior change || `chore` | Config, deps, tooling, maintenance || `test` | Adding or updating tests || `docs` | Documentation only || `style` | Formatting, whitespace || `perf` | Performance improvement || `ci` | CI/CD changes || `build` | Build system changes || `revert` | Reverting a previous commit |---## Workflow1. Read the user's description of changes.2. Ask: *"Do you have a ticket number for this?"* — if the user doesn't provide one, proceed without it.3. Infer the correct `type` from the nature of the changes.4. Generate the branch name following the convention above.---## Examples**User:** "I'm adding dark mode support" — Ticket: PROJ-312```feat/PROJ-312_dark_mode_support```---**User:** "fixing a crash on the payment screen" — No ticket```fix/payment_screen_crash```---**User:** "upgrading Flutter and fixing deprecated APIs" — Ticket: PROJ-548```feat/PROJ-548_flutter_upgrade```

Frequently asked questions