How do I install the Branch Name skill?

Run npx skillmds@latest add kin0992/branch-name 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 Branch Name 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 Branch Name?

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 Branch Name free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Branch Name?

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

Branch Name by kin0992 — Agent Skill

Name: Branch Name
Author: kin0992

Branch Name

**UTILITY SKILL** - Suggest a Git branch name following the <activity-type>/<activity-name> convention. USE FOR: name a branch, suggest branch name, create branch name from task description, generate git branch name, pick branch name for feature or fix. DO NOT USE FOR: writing commit messages (use commit-message), generating PR descriptions (use pr-title-description), naming releases or tags. INVOKES: nothing — derives the branch name from the task description provided by the user. FOR SINGLE OPERATIONS: Use git checkout -b directly when the name is already obvious.

kin0992 a6009a3 2.7 KB Updated Sep 17, 2026

File contents

Suggest a Git branch name

Propose a well-formed branch name from a task description, following the <activity-type>/<activity-name> convention.

Convention

<activity-type>/<activity-name>

Activity types

Type	Use for
`features`	New features
`fixes`	Any kind of fix
`refactors`	Code refactoring and reducing technical debt
`chores`	System tasks that are not user-facing
`docs`	Documentation-related tasks

Activity name rules

Lowercase, words separated by hyphens (-).
Short and meaningful — avoid generic words like update or fix.
Plural form where applicable, similar to naming a folder that groups related files (e.g., user-notifications rather than user-notification).
No tracking IDs (e.g., Jira issue keys). Reference them in the PR description instead.

Instructions

Identify the primary intent of the task description.
Pick the most specific activity type from the table above.
Derive a short, descriptive activity name: lowercase, hyphen-separated, plural where it makes sense.
If the task spans multiple unrelated concerns, suggest splitting into separate branches and propose one name per concern.
Never invent or include issue/ticket IDs.

Output

Return only the branch name, no commentary or fences. If multiple branches are warranted, list one per line with a one-sentence rationale for each.

Examples

features/dark-mode-settings

fixes/broken-pagination-links

refactors/auth-token-handlers

chores/dependency-upgrades

docs/api-authentication-guides

Common edge cases

If the task description contains an issue ID (e.g., PROJ-123), strip it and derive the name solely from the textual description.
If the description is too vague (e.g., "do the thing"), ask for clarification before proposing a name.
Hotfixes and security patches fall under fixes.

---name: branch-namedescription: **UTILITY SKILL** - Suggest a Git branch name following the <activity-type>/<activity-name> convention. USE FOR: name a branch, suggest branch name, create branch name from task description, generate git branch name, pick branch name for feature or fix. DO NOT USE FOR: writing commit messages (use commit-message), generating PR descriptions (use pr-title-description), naming releases or tags. INVOKES: nothing — derives the branch name from the task description provided by the user. FOR SINGLE OPERATIONS: Use git checkout -b directly when the name is already obvious.license: MIT---# Suggest a Git branch namePropose a well-formed branch name from a task description, following the`<activity-type>/<activity-name>` convention.## Convention```<activity-type>/<activity-name>```### Activity types| Type | Use for || ----------- | -------------------------------------------- || `features` | New features || `fixes` | Any kind of fix || `refactors` | Code refactoring and reducing technical debt || `chores` | System tasks that are not user-facing || `docs` | Documentation-related tasks |### Activity name rules- **Lowercase**, words separated by **hyphens** (`-`).- **Short and meaningful** — avoid generic words like `update` or `fix`.- **Plural form** where applicable, similar to naming a folder that groups related files (e.g., `user-notifications` rather than `user-notification`).- **No tracking IDs** (e.g., Jira issue keys). Reference them in the PR description instead.## Instructions1. Identify the primary intent of the task description.2. Pick the most specific activity type from the table above.3. Derive a short, descriptive activity name: lowercase, hyphen-separated, plural where it makes sense.4. If the task spans multiple unrelated concerns, suggest splitting into separate branches and propose one name per concern.5. Never invent or include issue/ticket IDs.## OutputReturn only the branch name, no commentary or fences.If multiple branches are warranted, list one per line with a one-sentencerationale for each.## Examples```textfeatures/dark-mode-settings``````textfixes/broken-pagination-links``````textrefactors/auth-token-handlers``````textchores/dependency-upgrades``````textdocs/api-authentication-guides```## Common edge cases- If the task description contains an issue ID (e.g., `PROJ-123`), strip it and derive the name solely from the textual description.- If the description is too vague (e.g., "do the thing"), ask for clarification before proposing a name.- Hotfixes and security patches fall under `fixes`.

Frequently asked questions