Skills Guide

Git Branch Naming

VerifiedSafe

Creates git branches with a standardized naming convention using type/short-description format. Use this skill when starting new work, switching to feature branches, or ensuring consistent branch naming across a project.

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

Recommended for

Backend developerClaude CodeCode reviewCursorFrontend developerCopilot

Our review

Creates git branches following a type/short-description naming convention to organize work.

Strengths

  • Clear and consistent naming for all team members
  • Automatic categorization of work type (feat, fix, docs, etc.)
  • Simplifies branch tracking and search

Limitations

  • Does not cover all possible cases (e.g., release branches)
  • No automatic validation without an additional hook
When to use it

When starting a new task or feature to create a branch with a standardized name.

When not to use it

When the team already uses another established naming convention or a specific workflow (e.g., Git Flow).

Security analysis

Safe
Quality score90/100

The skill only instructs creating a git branch using standard naming conventions and git commands. No destructive, exfiltrating, or unsafe actions.

No concerns found

Examples

Feature branch for infinite scroll
Create a branch for adding infinite scroll to the feed
Fix branch for album path validation
Create a branch to fix the album path validation bug
Chore branch for pre-commit hooks
Create a branch to add pre-commit hooks to the project

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

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin