skills.rest
bordenet
bordenetCOMMUNITY
Explore all skills by this author →
GitHub

git-branch-conventions

Validate new git work branch names against semantic prefix and formatting rules.

8|1|Updated Jan 24, 2026
Search Tags:#git#workflow#validation#branching#conventions#branch-naming#prefixes
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill git-branch-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-branch-conventions
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/git-branch-conventions
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill git-branch-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New work branches often use inconsistent or ambiguous names that hinder collaboration, CI rules, and triage; this Skill enforces a small set of semantic prefixes and formatting rules to keep branch names predictable and meaningful.

Core Features & Use Cases

  • Canonical prefixes: Requires one of feat/, fix/, exp/, doc/, perf/, or chore/ to communicate intent at a glance.
  • Formatting validation: Enforces lowercase, hyphen-separated short descriptions and supports optional ticket IDs for traceability.
  • Practical workflows: Helps developers name feature branches, bugfixes, experiments, docs, performance work, and maintenance branches consistently so PR reviews and CI gates behave reliably.

Quick Start

Ask the assistant to name and create a new work branch using a semantic prefix and hyphenated description, for example create a branch named feat/add-login.

Frequently Asked Questions about git-branch-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce semantic git branch naming conventions for new work branches?▼

To enforce semantic git branch naming, this Skill validates that new branches created with commands like git checkout -b or git switch -c use canonical prefixes such as feat/, fix/, or chore/ alongside lowercase hyphenated descriptions and optional ticket IDs.

What are the required prefixes for validating git branch names?▼

The required prefixes for validating git branch names are feat/, fix/, exp/, doc/, perf/, and chore/. These semantic prefixes communicate intent at a glance and keep branch names predictable for CI gates and triage.

How do I create a git branch with a ticket ID using naming conventions?▼

To create a git branch with a ticket ID, use a canonical prefix followed by a lowercase, hyphen-separated description and the optional ticket identifier. The Skill validates this formatting when you run commands like git branch or git worktree add -b.

Does this branch validation apply to permanent or release branches?▼

No, this branch validation targets new work branches rather than permanent or release branches. It intercepts branch creation commands like git checkout -b and git switch -c to enforce semantic prefixes and formatting on new work only.

Why should I use semantic prefixes for git branch naming?▼

You should use semantic prefixes for git branch naming because inconsistent names hinder collaboration, CI rules, and triage. Enforcing prefixes like fix/ or doc/ keeps branch names meaningful so PR reviews and CI gates behave reliably.

Can I use uppercase letters or spaces in my git branch descriptions?▼

No, the formatting validation rejects uppercase letters and spaces, requiring lowercase, hyphen-separated short descriptions instead. This ensures branch names remain consistent and compatible with standard git workflows.

Related Skills

Explore More Software Engineering Skills→
iani-kuliiani-kuli

create-branch

Create git branches with standardized names from user identity and diffs.

Community
Intermediate
gewoonsebagewoonseba
9

commit-push-pr

Automate Git commit, push, and pull request creation via gh.

Community
Intermediate
mauriciodelriomauriciodelrio
3

git-usage

Enforces Git commit message, branch naming conventions via commitlint and Husky.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate