git-branch-naming

Enforce branch naming format <type>/<area>/<topic> for AX-WMS monorepo.

Updated Jun 5, 2026

Search Tags:#git workflow #hotfix #branch naming #gitflow #branch-prefix #dev branch #web api ai infra docs

Ready to run

npx skills add https://github.com/KangJiSseok/ACODIAN --skill git-branch-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-branch-naming
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/git-branch-naming
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill git-branch-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AX-WMS 모노레포에서 브랜치 명명 규칙과 기본 브랜치 전략을 한곳에서 안내하고, 사용자가 브랜치 이름을 정하거나 어떤 브랜치를 파야 하는지 문의할 때 기준을 제공합니다.

Core Features & Use Cases

브랜치 구조 가이드: dev를 기본으로 한 릴리즈 흐름과 각 작업 유형의 역할을 설명합니다.
네이밍 규칙 제시: 형식 <type>/<area>/<topic>를 적용하고 소문자/슬래시 규칙을 강제합니다.
실전 예시: 예시로 feat/web/login-flow, fix/api/worklog-status, hotfix/master-긴급수정 등을 제공합니다.
브랜치 전략: hotfix/*는 master에서 관리하고 변경사항은 dev에도 반영하는 등의 운영 원칙을 안내합니다.

Quick Start

브랜치 이름 규칙에 맞춰 예시를 제시하고 기본 브랜치인 dev를 사용해 새 브랜치를 생성하는 방법을 안내해줘.

Frequently Asked Questions about git-branch-naming

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

FAQPage Schema

What is the standard git branch naming convention for a monorepo?▼

The standard git branch naming convention for a monorepo uses the format <type>/<area>/<topic> with strict lowercase letters and no spaces. Examples include feat/web/login-flow for new features and fix/api/worklog-status for bug fixes.

How do I manage a hotfix branch in a dev and master GitFlow strategy?▼

To manage a hotfix branch in a GitFlow strategy, fork directly from the master branch using the hotfix/* prefix. After applying the urgent fix, ensure the changes are merged back into both master and the dev branch to keep them synchronized.

Which base branch should I fork from when starting new work in a monorepo?▼

You should fork from the dev branch as the base when starting new work in a monorepo. The dev branch serves as the primary integration point for ongoing development across web, api, ai, infra, and docs applications before reaching master.

When should I use the hotfix branch prefix instead of a fix branch?▼

You should use the hotfix branch prefix when addressing urgent production issues that require immediate deployment from master. Standard fix branches are used for regular bug fixes based off the dev branch during normal development cycles.

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

No, you cannot use uppercase letters or spaces in git branch names under this rule set. The naming format <type>/<area>/<topic> strictly enforces lowercase letters and uses slashes to separate the branch type, application area, and specific topic.

What is the best way to structure branch names for different app areas like api and web?▼

The best way to structure branch names for different app areas is using the <type>/<area>/<topic> format. You specify the application area such as api, web, ai, infra, or docs in the middle segment, like feat/api/search-endpoint or docs/web/user-guide.