skills.rest
github
githubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

conventional-branch

Creates Git branches following the Conventional Branch naming specification.

38.5k|4.9k|Updated Jun 11, 2025
Search Tags:#Git#kebab-case#Branching Strategy#Git Workflow#Version Control#Branch Naming#conventional branch
One-click install
npx skills add https://github.com/github/awesome-copilot --skill conventional-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-branch
Source: https://github.com/github/awesome-copilot/tree/main/skills/conventional-branch
Command: npx skills add https://github.com/github/awesome-copilot --skill conventional-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent Git branch names make repositories hard to navigate and break automation that relies on naming conventions. This Skill enforces the Conventional Branch specification so every branch follows a predictable, validated format.

Core Features & Use Cases

  • Standardized Branch Types: Supports feature/, bugfix/, hotfix/, release/, and chore/ prefixes with aliases like feat/ and fix/.
  • Name Validation: Checks names against rules for lowercase, allowed characters, hyphen/dot placement, and description quality.
  • Base Branch Detection: Automatically detects the repository's trunk branch (main, master, or develop) before creating the new branch.
  • Use Case: When starting work on a new login feature, ask the assistant to create a branch and it will produce a compliant name like feature/add-login-page, branch off the detected trunk, and check it out.

Quick Start

Ask the assistant to create a new Git branch for your task using the Conventional Branch naming convention.

Frequently Asked Questions about conventional-branch

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

FAQPage Schema
How do I create a Git branch following Conventional Branch naming?▼

Use the format type/description, such as feature/add-login-page or bugfix/fix-header-bug. Valid types are feature, bugfix, hotfix, release, and chore, with feat and fix as accepted aliases.

What branch name prefixes are allowed in Conventional Branch?▼

The specification allows feature/ (alias feat/), bugfix/ (alias fix/), hotfix/, release/, and chore/. Trunk branches like main, master, and develop use no prefix at all.

Can I use dots or underscores in a Conventional Branch name?▼

Dots are allowed only in release version descriptions like release/v1.2.0. Underscores, spaces, and uppercase letters are never allowed; use lowercase kebab-case with hyphens instead.

Why is my branch name rejected by the Conventional Branch rules?▼

Common failures include uppercase letters, consecutive hyphens, leading or trailing hyphens, hyphen-dot adjacency, and unknown prefixes. Lowercase everything, replace spaces and underscores with hyphens, and collapse repeated hyphens.

How does Conventional Branch relate to Conventional Commits?▼

Conventional Branch complements Conventional Commits by aligning branch types with commit types. For example, a feature/add-login branch pairs with feat: commits, and a bugfix branch pairs with fix: commits.

Related Skills

Explore More Software Engineering Skills→
Ouro-labsOuro-labs
14

ce-clean-gone-branches

Identify and delete local branches with deleted remote tracking branches.

Official
Basic
shalevaminshalevamin

yeet

Stage, commit, and push code changes to a new branch and open a draft GitHub pull request.

Community
Intermediate
paulinett1508-devpaulinett1508-dev

branching-strategy

Standardize Git branching practices with naming, protection, and merge rules.

Community
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

git-storytelling-branch-strategy

Plan and manage git branches with naming conventions and workflow models.

Official
Intermediate