SkillsAdd

somnio-software/somnio-ai-tools

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".

First seen Mar 25, 2026

Installation

$ npx skills add somnio-software/somnio-ai-tools --skill git-branch-format
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

git-flow-branch-creator Similar name
github/awesome-copilot

Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branc…

9.6K installs
neon-postgres-branches Similar name
neondatabase/agent-skills

>- Choose and create the right Neon branch type for testing and development. Use when users ask…

5.9K installs
create-branch Similar name
getsentry/skills

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "…

3.7K installs
finishing-a-development-branch Similar name
obra/superpowers

Use when implementation is complete, all tests pass, and you need to decide how to integrate th…

181.3K installs
apifox-branch Similar name
apifox.com

Apifox 分支协作：普通分支、迭代分支、AI 分支、pick-to、merge、merge-request、保护分支、AI 写?

4.6K installs
new-branch-and-pr Similar name
cursor/plugins

Create a fresh branch, complete work, and open a pull request

1.8K installs

Also in this package

Other skills from somnio-software/somnio-ai-tools · top by installs.

npx skills add somnio-software/somnio-ai-tools
flutter-health-audit 136 security-audit 131 flutter-best-practices 128 workflow-builder 117 react-best-practices 111 nestjs-best-practices 111 nestjs-health-audit 109 git-commit-format 100 clockify-tracker 99 react-health-audit 96

Browse all from somnio-software/somnio-ai-tools

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,231 B
  • docs SUMMARY.md 453 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 101 installs

SKILL.md

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)
  • shortdescription is snakecase, max 3 words — prefer 1–2
  • Example: feat/TICKET-548flutterupgrade

Without ticket number

{type}/{short_description}
  • shortdescription is snakecase, 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

  1. 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