create-branch

Create and switch to a feature branch from a Jira ticket number.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nclandrei/dotfiles --skill create-branch-nclandrei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/nclandrei/dotfiles/tree/main/config/skills/create-branch
Command: npx skills add https://github.com/nclandrei/dotfiles --skill create-branch-nclandrei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a feature branch from a Jira ticket number, standardizing naming and reducing manual steps. The workflow ensures consistent branch names and reduces the chance of human error when starting work tied to Jira issues.

Core Features & Use Cases

  • Standardized branch naming based on Jira tickets (e.g., nclandrei-SECINT-111)
  • Automatic update of the main branch before branch creation
  • Create and switch to the new feature branch in a single, repeatable workflow

Quick Start

Create and switch to the feature branch for the given Jira ticket after updating the main branch.

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 feature branch from a Jira ticket automatically?

To create a git feature branch from a Jira ticket automatically, you provide the ticket number and the workflow updates the main branch, generates a deterministic branch name, and checks out the new branch.

What is the standard naming convention for git branches linked to Jira issues?

Standard naming convention for git branches linked to Jira issues uses a deterministic format combining your username and the Jira ticket number, such as username-TICKET-123, ensuring consistent and traceable branch names.

How do I update the main branch before creating a new feature branch?

To update the main branch before creating a new feature branch, the automated workflow pulls the latest changes from the main branch first, then creates and switches to the new feature branch in a single repeatable process.

Can I automate switching to a new git branch right after it is created from a Jira ticket?

Yes, you can automate switching to a new git branch right after it is created from a Jira ticket. The workflow handles both branch creation and checkout in a single step to reduce manual commands.

Does this Jira branch creation workflow require any specific git dependencies?

No specific git dependencies are required for this Jira branch creation workflow. It operates as a standalone automation tool that runs standard git commands to update the main branch and create the new branch.

Why should I use an automated workflow for creating feature branches from Jira tickets?

Using an automated workflow for creating feature branches from Jira tickets eliminates manual steps, enforces deterministic branch naming, and reduces the chance of human error when starting work tied to Jira issues.