Ready to generate
Fill in the title and click Generate// create kebab-case branch names in one click
Generate clean, kebab-case Git branch names from issue titles, task types, and scopes. Supports feature, fix, hotfix, chore, and more.
Ready to generate
Fill in the title and click GeneratePaste the issue title or task description from your project board.
Pick the branch type (feature, fix, hotfix…) and optionally add a scope like auth or ui.
Click ⎘ Copy on the primary result or pick a variant that fits your team's convention.
The Branch Name Generator converts human-readable issue titles into properly formatted Git branch names. It enforces kebab-case, removes special characters, and prefixes with your chosen type and optional scope — keeping branches clean and consistent across your team.
Most teams use type/short-description format (e.g., feature/add-dark-mode). Including a type prefix helps categorize work and integrates well with CI/CD pipelines. Some teams also prefix the issue number like feature/123-add-dark-mode.
Kebab-case means words are lowercase and separated by hyphens: add-dark-mode-toggle. It's the most widely supported format for Git branches across all operating systems and avoids issues with spaces or special characters in shell commands.
Including the issue number (e.g., feature/123-add-dark-mode) is highly recommended. It allows GitHub, GitLab, and Jira to automatically link the branch to the corresponding issue, giving you traceability without any extra effort.
The generator supports: feature (new functionality), fix (bug fixes), hotfix (urgent production fixes), chore (maintenance), refactor (code restructuring), docs (documentation), test (test coverage), style (formatting), perf (performance), and ci (CI/CD changes).
Keep branch names under 60–80 characters. Very long names are hard to read in terminal output and some Git hosting providers may truncate them in the UI. The tool defaults to 60 characters, which works well for most workflows.
Scope adds a namespace to your branch, e.g., feature/auth/add-oauth-login. It's useful in monorepos or large projects where multiple teams work on different subsystems. Leave it blank if your project doesn't use scopes.
A Branch Name Generator is a developer utility that converts plain-text issue titles, task descriptions, and feature requests into properly formatted Git branch names. Instead of manually typing feature/add-user-authentication-with-oauth-support, you paste your Jira or GitHub issue title and instantly get a clean, kebab-case branch name that follows your team's naming convention.
Consistent branch naming is one of those small practices that pays enormous dividends over time. It makes code review cleaner, CI/CD pipelines more predictable, and Git history far easier to navigate. Yet it's also one of those tasks that developers — under pressure to ship — often skip or inconsistently apply. This tool removes the friction entirely.
💡 Looking for premium web development assets? MonsterONE offers unlimited downloads of templates, UI kits, and developer assets — worth checking out.
In any team larger than one person, branch naming conventions are an invisible form of documentation. When you see hotfix/payment-gateway-timeout in a pull request list, you immediately know its urgency and purpose — no commit message or PR description required. Compare that to branches named johns-fix, temp2, or wip-feature, which tell you nothing.
Well-named branches also integrate seamlessly with project management tools. GitHub can automatically close issues when branches matching a pattern are merged. GitLab shows branch names in merge request threads. Jira detects branch names containing issue keys and links them to tickets in the activity feed — but only if your branches are named correctly.
A well-structured branch name typically consists of three to four parts:
feature, fix, hotfix, chore, refactor, docs, test, perf, style, or ci.auth, ui, api, checkout. Particularly useful in monorepos.123. Enables automatic issue tracking in GitHub, GitLab, and Jira.add-oauth-login, fix-null-pointer-exception.Combined, a complete branch name might look like: feature/auth/123-add-oauth-login or simply fix/123-null-pointer-on-checkout for teams that don't use scopes.
feature/ — New functionality being added to the codebase. This is the most common type. Examples: feature/user-profile-page, feature/export-to-csv.
fix/ — Fixes a bug in a non-critical path. The fix can go through the normal PR review process. Examples: fix/login-redirect-loop, fix/image-upload-validation.
hotfix/ — Urgent fix for a production-breaking issue. Typically branches off main or production directly, bypassing the normal sprint cycle. Examples: hotfix/payment-crash-on-checkout.
chore/ — Maintenance work that doesn't affect the user-facing product. Dependency updates, configuration changes, build script modifications. Examples: chore/upgrade-dependencies, chore/update-eslint-config.
refactor/ — Code restructuring without behavior changes. Examples: refactor/extract-auth-service, refactor/flatten-component-tree.
docs/ — Documentation-only changes. README updates, inline comment improvements, wiki additions. Examples: docs/add-api-reference, docs/update-setup-guide.
Git branch names can technically contain most characters, but in practice, only a few styles are universally safe. Kebab-case (add-dark-mode) is the de facto standard because it works identically on Windows, macOS, and Linux, is readable at a glance in terminal output, doesn't require escaping in shell scripts, and renders cleanly in GitHub/GitLab UIs.
Snake_case (add_dark_mode) is sometimes used but can be confused with Python module names. CamelCase (addDarkMode) is difficult to read in terminal and non-standard for branches. Spaces are technically valid in Git but require quoting in every shell command — avoid them entirely.
GitHub Flow — The simplest workflow: branch off main, work, open a pull request, merge. Branch names like feature/add-dark-mode work perfectly here.
Gitflow — More structured, with develop, release/, hotfix/, and feature/ branches. This tool's type prefixes map directly to Gitflow's branch categories.
Trunk-Based Development — Short-lived feature branches off main, merged quickly. Consistent naming is even more important here because branches are created and deleted frequently.
The generator applies a series of transformations to your input title. First, it lowercases the entire string. Then it replaces spaces and underscores with hyphens. Next, it strips any characters that aren't letters, numbers, or hyphens. Consecutive hyphens are collapsed into a single one. Leading and trailing hyphens are removed. Finally, the result is trimmed to your specified maximum length, taking care not to cut in the middle of a word.
The type, scope, and issue number are prepended after this transformation, using either slash-separated format (feature/auth/123-description) or hyphen-separated format (feature-auth-123-description) depending on your preference.