
Branch Name Generator
Turn a messy task description into a clean, conventional git branch name: detects the type (feature, fix, refactor), slugifies the summary, pulls in JIRA/GitHub ticket prefixes, then offers to run git checkout -b for you. One naming standard the whole team actually follows, instead of 'quick-fix-1'.
- Standardize branch naming across a distributed engineering team
- Automatically extract and format JIRA/GitHub tickets into branch names
- Categorize commits into features, fixes, or chores via intelligent detection
$5
· or 25 creditsSecure checkout via Stripe
Included in download
- Standardize branch naming across a distributed engineering team
- Automatically extract and format JIRA/GitHub tickets into branch names
- terminal automation included
- Includes example output and usage patterns
Sample input
Make a branch for PRJ-123 implement user auth provider feature.
Sample output
Branch name:
PRJ-123-feature/user-auth-provider
Create this branch now?
yes Switched to a new branch 'PRJ-123-feature/user-auth-provider'
Turn a messy task description into a clean, conventional git branch name: detects the type (feature, fix, refactor), slugifies the summary, pulls in JIRA/GitHub ticket prefixes, then offers to run git checkout -b for you. One naming standard the whole team actually follows, instead of 'quick-fix-1'.
$5
· or 25 creditsSecure checkout via Stripe
Also available in a bundle
Included in download
- Standardize branch naming across a distributed engineering team
- Automatically extract and format JIRA/GitHub tickets into branch names
- terminal automation included
- Includes example output and usage patterns
- Instant install
Sample input
Make a branch for PRJ-123 implement user auth provider feature.
Sample output
Branch name:
PRJ-123-feature/user-auth-provider
Create this branch now?
yes Switched to a new branch 'PRJ-123-feature/user-auth-provider'
About This Skill
What it does
Transform messy task descriptions into standardized, professional Git branch names instantly. This skill automates the logic behind branch naming conventions, handling type detection (feature, fix, refactor, etc.), slugification, and ticket prefixing without manual editing.
Why use this skill
Consistency is key to a clean repository, but manual naming leads to "quick-fix-1" or "bug-stuff". This skill ensures every developer on your team follows the same strict format. It replaces the cognitive load of "What should I name this?" with a automated workflow that even offers to execute the git checkout -b command for you.
Supported workflows
- Intelligent Detection: Automatically categorizes work into fix, feature, hotfix, docs, refactor, test, or chore.
- Ticket Integration: Recognizes and formats project keys like JIRA tags or GitHub issue numbers.
- Clean Slugs: Lowercases, removes noise words, and sanitizes punctuation for terminal-safe names.
- Atomic Execution: One-click (or one-word) branch creation after name generation.
The output is a precise shell command ready for execution, ensuring your local environment stays in sync with your task tracking system.
Use Cases
- Standardize branch naming across a distributed engineering team
- Automatically extract and format JIRA/GitHub tickets into branch names
- Categorize commits into features, fixes, or chores via intelligent detection
- Reduce context switching by creating branches directly from natural language
Known Limitations
- Creates branches locally only (does not push to remote)
- Branch names limited to valid git characters (alphanumeric, hyphens, underscores, slashes)
- Ticket number detection requires format like "issue #42" or "JIRA-123"
- Does not check if branch already exists (git will error, skill catches and reports)
- Type detection is heuristic-based (may misclassify ambiguous descriptions)
How to Install
mkdir -p ~/.claude/skills && curl -sL https://www.agensi.io/api/install/branch-name-generator -o /tmp/branch-name-generator.zip && unzip -o /tmp/branch-name-generator.zip -d ~/.claude/skills && rm /tmp/branch-name-generator.zipFree skills install directly. Paid skills require purchase - use the download button above after buying.
Reviews
No reviews yet - be the first to share your experience.
Only users who have downloaded or purchased this skill can leave a review.
Early access skill
Be the first to review this skill.
Only users who have downloaded or purchased this skill can leave a review.
Security Scanned
Passed automated security review
Permissions
Branch Name Generator needs terminal access only when user confirms "create this branch now." In that case, it runs `git checkout -b {branch-name}`. If the user only wants a suggestion without creating the branch, no terminal access is used. No file, browser, network, or environment access required.
Works with Claude Code and Codex. Requires git in PATH. Creates branches locally (does not push to remote unless user manually runs `git push -u origin branch-name`).
Creator
JustHandled Labs builds focused agent skills for the work nobody wants to do by hand. Each one is a single repeatable job done well: catching the security and data mistakes that quietly ship, keeping docs and tests honest, gating the commands an agent is about to run, sharpening writing, and handling the founder chores around launches, outreach, and brand setup. Not generic AI productivity. Specific workflows that are easy to run, review, and repeat. Maintained by H.J. Westerfield, with a background in communications, editing, project coordination, customer support, and practical AI systems. Tools for people who want useful automation without theatrical complexity.
Also available in a bundle
Frequently Asked Questions
Learn More About AI Agent Skills
More Premium Skills
Multi-Agent Orchestration Master Library
Transform Claude Code into a coordinated multi-agent system. Battle-tested tmux orchestration patterns, YAML task queues, event-driven communication, and parallel worker management for 8+ agents.

inline-comment
Best way to steer your agents, effortlessly.

Legacy Code Modernization Planner for AI Coding Agents
Creates safe modernization roadmaps for old, messy, undocumented, or fragile codebases, including risk audits, refactor phases, dependency reviews, testing plans, migration steps, and AI coding prompts.
designing-hybrid-context-layers
Architects the right retrieval strategy for every query — teaching your agent when to use RAG, a knowledge graph, or a temporal index instead of defaulting to vector search for everything.