git-branch-practices

Enforce standard git branch naming with type prefixes and lowercase hyphenated descriptions.

Updated Nov 29, 2025

Search Tags:#git #workflow #collaboration #conventions #version-control #branch-naming

Ready to run

npx skills add https://github.com/thimslugga/agent-skills --skill git-branch-practices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-branch-practices
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/git/git-branch-naming-best-practices
Command: npx skills add https://github.com/thimslugga/agent-skills --skill git-branch-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch naming inconsistencies slow collaboration and increase review friction; this skill provides a standardized approach and practical guidelines for naming git branches.

Core Features & Use Cases

Enforces a <type>/<description> format with common prefixes: feature/, bugfix/, hotfix/, release/, refactor/, docs/, test/, chore/.
Provides practical examples, rules (lowercase, hyphens, avoid vague names, include ticket IDs when available), and quick references for teams.
Supports workflow guidance across various Git workflows and integrates with hooks or CI to encourage consistent naming.

Quick Start

Tell me a branch name you want to use, and I will validate it against the approved prefixes and format.

Frequently Asked Questions about git-branch-practices

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

FAQPage Schema

What are standard git branch naming conventions for team collaboration?▼

Valid git branch names must follow a <type>/<description> format using approved prefixes such as feature/, bugfix/, hotfix/, release/, refactor/, docs/, test/, or chore/. Descriptions must be lowercase, hyphenated, and include ticket IDs when available.

How do I enforce consistent git branch naming in a CI workflow?▼

You can enforce consistent git branch naming in CI by validating branches against approved prefixes and a <type>/<description> format. This skill provides rules and workflow guidance that integrate with hooks or CI pipelines to reject non-compliant names automatically.

What prefixes should I use for feature branches versus hotfix branches?▼

Use the feature/ prefix for new functionality and the hotfix/ prefix for urgent production fixes. Both require a lowercase, hyphenated description following the prefix, and should include an optional ticket ID to maintain clear version-control history.

Why use hyphens and ticket IDs in git branch names?▼

Using hyphens and ticket IDs in git branch names prevents ambiguous references and links work directly to project tracking. Hyphens ensure readable lowercase descriptions, while ticket IDs provide traceability for collaboration and faster code reviews.

Does this branch naming guidance work with existing Git workflows?▼

Yes, this branch naming guidance supports integration across various Git workflows. It provides standard prefixes and format rules that apply universally, helping teams standardize branch naming conventions without overhauling their existing version-control processes.

How do I validate a proposed git branch name against naming rules?▼

To validate a git branch name, check it against the required <type>/<description> format and approved prefixes like chore/ or docs/. Ensure the description uses lowercase words separated by hyphens, avoids vague terms, and includes a ticket ID if available.