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.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude CodeCursorWindsurfCopilotCodex
#git#branch-naming#naming-conventions#workflow

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorCopilot

Automated summary

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

How this analysis is made

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-branch-naming-mmio71c4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-branch-naming-mmio71c4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-branch-naming-mmio71c4/download' --output '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md.part' && mv '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md.part' '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mmio71c4' '.claude/skills/branch'

Cursor
test -f '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mmio71c4' '.cursor/skills/branch'

Codex
test -f '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && test -s '.skill-downloads/git-branch-naming-mmio71c4/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/branch' && cp -R '.skill-downloads/git-branch-naming-mmio71c4' '.agents/skills/branch'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-branch-naming-mmio71c4'

openskills read 'git-branch-naming-mmio71c4'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-branch-naming-mmio71c4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot