jira-git-checkout-branch

Create and check out a Jira-based git branch from an In Progress issue.

9|Updated Dec 21, 2016

Search Tags:#git #workflow #mcp #jira #atlassian #branch #checkout

Ready to run

npx skills add https://github.com/ysoftman/myenv --skill jira-git-checkout-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-git-checkout-branch
Source: https://github.com/ysoftman/myenv/tree/main/.claude/skills/jira-git-checkout-branch
Command: npx skills add https://github.com/ysoftman/myenv --skill jira-git-checkout-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Picking up an In Progress Jira issue and turning it into a corresponding Git branch, then checking out that branch to start work, helps maintain traceability between Jira and code and avoids manual naming errors.

Core Features & Use Cases

Selects an In Progress Jira issue assigned to the user and derives a branch name from the issue key.
Creates and checks out a new local branch that begins with the Jira key, following ASCII lowercase with hyphens, capped at 50 characters.
Validates working tree state, checks MCP availability, and prompts for confirmation when needed.
Use case: You want to begin work on a Jira In Progress task by aligning your Git branch name with the issue key, ensuring traceability in code and boards.

Quick Start

Create a Jira-based git branch from your In Progress issue by asking your assistant to perform the operation.

Frequently Asked Questions about jira-git-checkout-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 In Progress issue?▼

To create a git branch from a Jira In Progress issue, this automation derives a branch name from the issue key and checks it out locally. It enforces ASCII lowercase hyphenated naming, caps length at 50 characters, and requires a clean working tree.

Do I need Atlassian MCP tools to automate Jira branch checkout?▼

Yes, you need Atlassian MCP tools and Jira cloud access to automate Jira branch checkout. The process checks MCP availability before execution and selects an In Progress issue assigned to you to generate the corresponding branch.

What happens if my working tree is dirty when creating a Jira-based branch?▼

If your working tree is dirty, the Jira-based branch creation process will trigger safety checks and prompt for confirmation. It requires a clean working tree to ensure no uncommitted changes are lost during the checkout operation.

What are the naming rules for a git branch generated from a Jira issue key?▼

Git branches generated from a Jira issue key must begin with the Jira key, use ASCII lowercase with hyphens, and are capped at 50 characters. These rules maintain traceability between your code and Jira boards.

Can I automatically select my assigned In Progress Jira issues for branch creation?▼

Yes, you can automatically select your assigned In Progress Jira issues for branch creation. The workflow identifies issues assigned to the user, derives the branch name, and performs the checkout with necessary safety validations.

Why does my Jira branch creation fail during git checkout?▼

Jira branch creation fails during git checkout if the working tree is dirty, MCP tools are unavailable, or Jira cloud access is missing. The process enforces these prerequisites to prevent data loss and ensure successful branching.