Git Branch Naming

VerifiedSafe

Creates Git branches with consistent naming using type/description format. Comprehensive guide with branch types and practical examples.

Sby Skills Guide Bot
DevelopmentBeginner
306/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#branching#naming-convention#workflow

Recommended for

Our review

Creates git branches using a structured naming convention (type/short-description) to maintain consistency in version control.

Strengths

  • Enforces a clear branch naming standard.
  • Categorizes work by type (feat, fix, etc.).
  • Encourages concise descriptive slugs.
  • Integrates seamlessly with git workflows.

Limitations

  • Only covers branch creation, not merging or other git operations.
  • Requires adherence to the defined types to be effective.
  • May need customization for teams with different conventions.
When to use it

Use when starting a new feature, bug fix, or any task that requires a new git branch.

When not to use it

Avoid when working on branches already created or when the team uses a different naming convention.

Security analysis

Safe
Quality score85/100

The skill only advises running 'git checkout -b' with a naming convention, which is a standard, non-destructive version control operation. No harmful commands, external network calls, data exfiltration, or safety bypasses are present.

No concerns found

Examples

Create feature branch
Create a new git branch for a user profile page feature. Use the proper naming convention.
Create fix branch
I need to fix a bug with login validation. Create a branch for this fix using the branching skill.
Create chore branch
Set up a branch for updating dependencies (chore). Use the type/short-description format.

name: branch description: Creates git branches with proper naming. Use when creating branches, starting new work, or switching to feature branches.

Branch Naming

Use type/short-description format.

Types

  • feat: User-facing features or behavior changes (must change production code)
  • fix: Bug fixes (must change production code)
  • docs: Documentation only
  • style: Code style/formatting (no logic changes)
  • refactor: Code restructuring without behavior change
  • test: Adding or updating tests
  • chore: CI/CD, tooling, dependency bumps, configs (no production code)

Examples

feat/infinite-scroll
fix/album-path-validation
refactor/state-management
chore/pre-commit-hooks
docs/update-readme
test/e2e-login-flow

Instructions

  1. Determine the type based on what the work will accomplish
  2. Choose a short, descriptive slug (2-4 words, hyphenated)
  3. Create the branch: git checkout -b type/short-description
Related skills