branch-naming

Standardize Git branch names with prefixes and Issue numbers.

2|Updated Nov 12, 2025

Search Tags:#git #workflow #branch #naming #conventional-commits #prefix #issue-number

Ready to run

npx skills add https://github.com/stlwolf/ai-development-hub --skill branch-naming-stlwolf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-naming
Source: https://github.com/stlwolf/ai-development-hub/tree/main/canonical/skills/branch-naming
Command: npx skills add https://github.com/stlwolf/ai-development-hub --skill branch-naming-stlwolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ブランチ命名規則を適用することで、開発チームのブランチ作成時の混乱を削減し、作業の追跡性を高めます。

Core Features & Use Cases

ブランチ命名規則の統一: prefix、Issue番号、命名フォーマットを定義し、全員が同じ形式でブランチを作成できる。
ワークフローの向上: feature、fix、ui などのプリフィックスを用いて作業カテゴリを即座に識別可能。
Use Case: 新機能開発のブランチを feature/1234_new-api-create のように命名して、対応する Issue を紐づける。

Quick Start

Create a new branch using an appropriate prefix and the related Issue number, e.g., feature/1234_add-user-auth.

Frequently Asked Questions about branch-naming

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

FAQPage Schema

How do I enforce consistent Git branch naming across teams?▼

Enforcing consistent Git branch naming requires standardizing prefix mapping, mandating an associated Issue number, and supporting formats like feature/1234_description. This approach prevents ambiguity in Git workflows and improves task traceability across feature development and bug fixes.

What is the best way to structure a Git branch name for feature development?▼

Structuring a Git branch name for feature development involves combining a category prefix, an Issue number, and a description, such as feature/1234_add-user-auth. This format immediately identifies the work category and links the branch to its corresponding tracking Issue.

What Git branch prefixes should I use for bug fixes and UI changes?▼

Git branch prefixes for bug fixes and UI changes typically include fix and ui. Using these specific prefixes standardizes branch naming conventions, allowing teams to instantly categorize and identify maintenance tasks within the software project workflow.

Can I link a Git branch to an Issue number using naming conventions?▼

Linking a Git branch to an Issue number using naming conventions is achieved by embedding the Issue ID directly in the branch name. This requires an associated Issue number within the branch string, ensuring immediate traceability between code changes and tracked tasks.

Why does standardizing branch naming prevent ambiguity in Git workflows?▼

Standardizing branch naming prevents ambiguity in Git workflows by enforcing a uniform prefix and format structure for all created branches. This standardization eliminates inconsistent naming patterns, reducing confusion and enhancing collaborative software project tracking.

Do I need an Issue number to create a branch with conventional naming?▼

Yes, an Issue number is required to create a branch with this conventional naming format. The system enforces prefix mapping to conventions and mandates an associated Issue number to ensure every branch is explicitly tied to a tracked development task.