git-branch-naming

Generate compliant git branch names with type prefixes and base branches.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill git-branch-naming-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-branch-naming
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/git-branch-naming
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill git-branch-naming-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common frustration of developers creating inconsistent, non-compliant branch names for the AX-WMS monorepo, which causes messy git history, misplaced pull requests, and confusion over correct base branches for work.

Core Features & Use Cases

  • Standardized Naming Rules: Enforces the project's lightweight GitFlow branch strategy with clear type prefixes (feat, fix, chore, etc.) and valid area categories (web, api, ai, infra, docs, agent).
  • Base Branch Guidance: Automatically recommends the correct base branch (dev for standard work, master for hotfixes) for every branch type.
  • Use Case: If a developer is working on a new login flow feature for the web app, the Skill will recommend the compliant branch name feat/web/login-flow and confirm it should be branched from dev.

Quick Start

Ask the Skill to recommend a compliant branch name for your current task, specifying the type of work you are doing and the app area you are modifying.

Frequently Asked Questions about git-branch-naming

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

FAQPage Schema
How do I generate a compliant git branch name for a monorepo feature task?

To generate a compliant git branch name for a monorepo feature, specify the work type and app area. The Skill outputs a standardized name like feat/web/login-flow, combining the correct type prefix and area category to enforce a lightweight GitFlow strategy.

What are the valid type prefixes and area categories for git branch naming in this workflow?

Valid git branch naming prefixes include feat, fix, refactor, chore, docs, and hotfix. Supported area categories are web, api, ai, infra, docs, and agent, ensuring every branch name aligns with the monorepo's standardized development workflow.

When do I branch from master instead of dev in a GitFlow strategy?

You branch from master instead of dev when creating hotfixes in a GitFlow strategy. Standard feature, bug fix, refactor, and chore branches should target dev as their base branch to maintain a clean git history.

Can I use this branch naming convention for a new API endpoint task?

Yes, you can use this branch naming convention for an API endpoint task. The Skill supports the api area category, delivering a compliant branch name like feat/api/your-endpoint and confirming the correct dev base branch for your pull request.

Why do my pull requests keep getting misplaced in the monorepo?

Pull requests get misplaced in the monorepo due to inconsistent git branch naming and incorrect base branch targets. Enforcing standardized branch names with correct type prefixes and base branches eliminates this confusion and ensures proper code collaboration.

Does this branch naming tool support documentation and infrastructure tasks?

Yes, this branch naming tool supports documentation and infrastructure tasks. It generates compliant branch names using the docs or infra area categories with appropriate type prefixes, ensuring all common development tasks follow the GitFlow strategy.