Create Branch

Git branch naming guidelines. Use when creating, renaming, or checking out new branches. Use when this capability is needed.

tomevault-io Updated

File contents

Git Branch Naming Guidelines

Follow the Conventional Branch specification with these details:

Prefixes

Except for main, all branch names must use one of:

  • feat/: New features (e.g., feat/add-login-page)
  • fix/: Bug fixes (e.g., fix/header-bug)
  • hotfix/: Urgent fixes (e.g., hotfix/security-patch)
  • release/: Release preparation (e.g., release/v1.2.0)
  • chore/: Non-code tasks (e.g., chore/update-dependencies)

Additional Rules

  • Include ticket numbers when applicable (e.g., feat/issue-123-new-login)
  • Dots allowed only for version numbers in release/ branches
  • Check existing branches for naming patterns before creating new ones
  • Do NOT use git -C <path> when the current directory is already the repository root

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/jmfontaine--jmf-claude-plugins--create-branch commit 43becb40ee

Frequently asked questions

npx skillmds@latest add tomevault-io/create-branch-3