How do I install the Git Branch skill?

Run npx skillmds@latest add puku0x/git-branch-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Branch safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Branch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Branch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Branch?

puku0x (@puku0x) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Branch by puku0x — Agent Skill

Name: Git Branch
Author: puku0x

Git Branch

Create Git branches with automatic type detection and project-specific naming conventions. Use when asked to "create a branch", "make a new branch", "create branch for changes", or when ready to organize code changes into a new branch. Supports feat, fix, docs, refactor, test, build, ci, chore, revert, and perf branch types with automatic type selection based on changed file patterns.

puku0x 78f74e0 2 files · 3.8 KB Updated Sep 17, 2026

File contents

Git Branch Skill

This skill guides the creation of Git branches with project-specific naming conventions.

When to Use

Use this skill when:

You have made changes to the codebase and need to create a new branch for those changes.
You want to ensure that the branch name follows the project's naming conventions.

Instructions

Step 1: Check staged changes

Use the following command to view staged changes:

git diff --staged

Important If there are staged changes, proceed to the next step.

If there are no staged changes, check unstaged changes with:

git diff --name-only

Step 2: Determine branch type and description

The format for branch names is:

<type>-<description>

If there are only staged changes, base the branch name on the staged changes.
If there are only unstaged changes, base the branch name on the unstaged changes.
If there are both staged and unstaged changes, base the branch name on the staged changes.

type is determined based on the patterns of the changed files:

feat-: New features or changes to existing features
fix-: Bug fixes
refactor-: Refactoring (changes that do not add features or fix bugs)
test-: Adding or modifying tests (e.g., changes to *.spec.* or *.spec.*.snap files)
docs-: Documentation-only changes (e.g., changes to *.md files)
ci-: CI-related changes (e.g., changes to files in .github/workflows/* or .github/actions/*)
chore-: Other changes (e.g., changes to *.json, configuration files like *.config.js, .gitignore, etc.)
revert-: Reverting previous commits
build-: Changes related to the build system or external dependencies
perf-: Performance improvements

description should concisely describe the changes made, using hyphens to separate words.

Step 3: Create the branch

Use git switch -c to create and switch to the new branch.

Example:

git switch -c feat-user-authentication

[!NOTE]

When the name of the branch already exists, append a unique suffix to the branch name to avoid conflicts. For example, if feat-user-authentication already exists, create feat-user-authentication-1, feat-user-authentication-2, etc.

References

branch-name.md

---name: git-branch-2description: Create Git branches with automatic type detection and project-specific naming conventions. Use when asked to "create a branch", "make a new branch", "create branch for changes", or when ready to organize code changes into a new branch. Supports feat, fix, docs, refactor, test, build, ci, chore, revert, and perf branch types with automatic type selection based on changed file patterns.---# Git Branch SkillThis skill guides the creation of Git branches with project-specific naming conventions.## When to UseUse this skill when:- You have made changes to the codebase and need to create a new branch for those changes.- You want to ensure that the branch name follows the project's naming conventions.## Instructions### Step 1: Check staged changesUse the following command to view staged changes:```bashgit diff --staged```**Important** If there are staged changes, proceed to the next step.If there are no staged changes, check unstaged changes with:```bashgit diff --name-only```### Step 2: Determine branch type and descriptionThe format for branch names is:```<type>-<description>```- If there are only staged changes, base the branch name on the staged changes.- If there are only unstaged changes, base the branch name on the unstaged changes.- If there are both staged and unstaged changes, base the branch name on the staged changes.**type** is determined based on the patterns of the changed files:- `feat-`: New features or changes to existing features- `fix-`: Bug fixes- `refactor-`: Refactoring (changes that do not add features or fix bugs)- `test-`: Adding or modifying tests (e.g., changes to `*.spec.*` or `*.spec.*.snap` files)- `docs-`: Documentation-only changes (e.g., changes to `*.md` files)- `ci-`: CI-related changes (e.g., changes to files in `.github/workflows/*` or `.github/actions/*`)- `chore-`: Other changes (e.g., changes to `*.json`, configuration files like `*.config.js`, `.gitignore`, etc.)- `revert-`: Reverting previous commits- `build-`: Changes related to the build system or external dependencies- `perf-`: Performance improvements**description** should concisely describe the changes made, using hyphens to separate words.## Step 3: Create the branchUse `git switch -c` to create and switch to the new branch.Example:```bashgit switch -c feat-user-authentication```> [!NOTE]>> When the name of the branch already exists, append a unique suffix to the branch name to avoid conflicts. For example, if `feat-user-authentication` already exists, create `feat-user-authentication-1`, `feat-user-authentication-2`, etc.## References- [branch-name.md](./references/branch-name.md)

Frequently asked questions