Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From base
Create a git branch with an appropriate name derived from current changes. Use when the user asks to create a branch, name a branch, make a branch for current work, or wants to move changes to a new branch. Also use when changes exist on main/master that should be moved to a feature branch before committing.
npx claudepluginhub kkhys/claude-code-marketplaceHow this skill is triggered — by the user, by Claude, or both
Slash command
/base:creating-branch-nameThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the current git state — uncommitted changes, staged files, and recent commits — to generate a branch name that communicates the intent of the work at a glance.
Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.
Creates git branches following Sentry naming conventions. Automatically determines branch type and description from arguments or local diff. Useful when starting new work.
Creates and switches to a new Git branch from an inline description, conversation context, or local diffs. Preserves uncommitted changes. Use for starting fresh or moving in-progress work to a named branch.
Share bugs, ideas, or general feedback.
Analyze the current git state — uncommitted changes, staged files, and recent commits — to generate a branch name that communicates the intent of the work at a glance.
A branch name is a communication tool. When a teammate sees feature/add-oauth-login in a PR list, they immediately know what it's about without opening it. The name should answer "what kind of change is this?" (the type prefix) and "what does it do?" (the description).
Format: <type>/<description>
Types:
feature/ — New capability or user-facing behaviorfix/ — Correcting broken behaviorrefactor/ — Restructuring without changing behaviordocs/ — Documentation onlystyle/ — Visual or formatting changes (CSS, code style)chore/ — Tooling, config, dependencies, CIDescription: English, kebab-case, 2-4 words that capture the main intent. Prefer starting with a verb (add, update, remove, implement, extract) when it reads naturally — but for fix/ branches, describing the problem (e.g., pagination-off-by-one) is often clearer than repeating the verb.
Example 1:
Changes: New login form component + auth API integration
Branch: feature/add-login-authentication
Example 2:
Changes: Fix off-by-one error in pagination
Branch: fix/pagination-off-by-one
Example 3:
Changes: Move utility functions into shared module
Branch: refactor/extract-shared-utils
Example 4:
Changes: Update ESLint config + reorder imports + add README section
Branch: chore/update-eslint-and-cleanup (mixed changes — name for the dominant intent)
git status, git diff --stat, git log as needed) to understand what changedgit checkout -b <name>After creation, briefly state the branch name and the reasoning behind it.