create-branch

Create a git branch from a Jira ticket key and issue summary slug.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shysssthanhtri/AI-tools --skill create-branch-shysssthanhtri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/create-branch
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill create-branch-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, consistent git branch names from Jira tickets to reduce manual naming errors, improve traceability, and enforce team branch conventions.

Core Features & Use Cases

  • Automatic branch naming: Build a feature/ticket-id-slug branch name derived from the Jira key and a concise slug of the issue summary.
  • Deterministic slug generation: Normalize summaries by lowercasing, replacing ampersands, removing punctuation, excluding filler words, truncating to a maximum length, and collapsing repeated dashes to produce repeatable slugs.
  • Jira validation and safe branching: Resolve a Jira cloud via Atlassian MCP, fetch the issue summary for accuracy, and create the new branch from the current checked-out branch to avoid branching from the default by mistake.
  • Use Case: When starting work on a Jira ticket, generate a readable branch that links code changes to the ticket without manual editing.

Quick Start

Create a branch for Jira ticket BK-123 from the current branch using the create-branch skill.

Frequently Asked Questions about create-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git branch from a Jira ticket automatically?

To create a git branch from a Jira ticket, this skill fetches the issue summary via Atlassian MCP and combines the ticket key with a normalized slug to generate a consistent feature branch name from your current checked-out branch.

What is the best way to normalize Jira issue summaries for git branch naming?

Normalizing Jira summaries for git branch naming involves lowercasing text, replacing ampersands, removing punctuation, excluding filler words, truncating to a maximum length, and collapsing repeated dashes to produce deterministic slugs.

Does this branching workflow require Atlassian MCP integrations to fetch Jira issue details?

Yes, resolving Jira issues and fetching accurate summaries requires Atlassian MCP integrations, which validate the ticket and supply the text needed to generate the deterministic slug for your branch name.

Can I create a new git branch from my current checked-out branch instead of the default?

Yes, this workflow creates the new Jira-derived branch directly from your current checked-out branch, ensuring you avoid mistakenly branching from the default branch and maintaining local developer workflow consistency.

Why should I use automated branch naming from Jira tickets instead of manual editing?

Automated branch naming from Jira tickets reduces manual naming errors, improves traceability between code changes and issues, and enforces consistent team branch conventions without requiring manual text editing.

What are the limitations of using deterministic slug generation for git branches?

Deterministic slug generation truncates summaries to a maximum length and removes specific punctuation, meaning highly descriptive Jira summaries will be shortened, potentially losing context in the final git branch name.