create-branch

Create Git feature branches from origin/main with strict naming conventions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JetBrains/databao-cli --skill create-branch-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/JetBrains/databao-cli/tree/main/.claude/skills/create-branch
Command: npx skills add https://github.com/JetBrains/databao-cli --skill create-branch-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating branches for new work can be error-prone and inconsistent. This skill standardizes branch names, ensures you branch from main, and protects against losing work by guarding uncommitted changes.

Core Features & Use Cases

  • Nickname-based branch naming derived from user identity and ticket metadata
  • Safe branching from origin/main with guardrails to prevent overwriting or losing work
  • Automatic handling for tickets with or without IDs, including naming formats like <nickname>/DBA-123-fix-auth-timeout
  • Use Case: Starting work on DBA-123 with your nickname to create a correctly formatted branch from origin/main

Quick Start

Ask the agent to create a branch for a ticket using your nickname and the standard nickname/ticket-descriptive format.

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 main with a consistent naming convention?

To create a Git feature branch from main, this skill automates safe branching from origin/main and derives a standardized branch name using your nickname and ticket metadata, ensuring consistent naming conventions.

What happens to uncommitted changes when I create a new Git branch?

Creating a new Git branch with uncommitted changes is guarded against data loss, as this skill applies guardrails to prevent overwriting or losing your work before branching from origin/main.

How do I format a Git branch name when my ticket has no ID?

For tickets without an ID, this skill automatically handles branch-name derivation to generate an appropriate naming format, using your nickname and descriptive text instead of requiring a ticket identifier.

What is the best way to standardize branch names across a development team using Git?

Standardizing branch names across a team is achieved by deriving consistent branch naming from user identity nicknames and ticket metadata, ensuring every feature branch follows the same format from origin/main.

Can I use my nickname to automatically generate a Git branch name from a ticket?

Yes, you can use your nickname to automatically generate a Git branch name from a ticket, producing a correctly formatted string like <nickname>/ticket-descriptive-name based on your identity and ticket metadata.