Skills Guide

Git Branch Naming

VerifiedSafe

Enforces a git branch naming convention using a type/short-description format, with predefined types such as feat, fix, or docs. Use this rule when creating or switching to branches to ensure consistent and descriptive branch names across the repository.

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

Recommended for

Backend developerClaude CodeCode reviewCursorFrontend developerCopilot

Our review

Creates Git branches with a standardized naming convention.

Strengths

  • Ensures consistency in branch names across a team.
  • Makes it easy to quickly identify the type of work (feat, fix, etc.).
  • Uses short, descriptive slugs for better readability.

Limitations

  • Does not handle branches with ticket or issue IDs (e.g., JIRA-123).
  • The nomenclature is limited to a few predefined types, which can be inflexible.
When to use it

Use this skill whenever you need to create a new Git branch to start a task.

When not to use it

Avoid using it if your branches require a different convention (e.g., including a ticket ID) or if you are working on an existing branch without creating a new one.

Security analysis

Safe
Quality score88/100

The skill only instructs creating a git branch using 'git checkout -b', which is a standard, non-destructive version control command. No external data exfiltration, destructive system commands, or credential leakage is involved.

No concerns found

Examples

Create a feature branch
Create a new branch for adding search pagination feature.
Create a fix branch
I need to fix the year search bug. Create a branch for that.
Create a chore branch
Create a branch to update pre-commit hooks.

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/search-pagination
fix/year-search-bug
chore/pre-commit-hooks
docs/update-readme
refactor/simplify-dynamo-queries
test/integration-coverage

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