skills.rest
maarten00
maarten00COMMUNITY
Explore all skills by this author →
GitHub

create-branch

Generates git branch names following repository-specific prefix and kebab-case conventions.

Updated Feb 24, 2025
Search Tags:#git#workflow#version control#conventional commits#github#kebab-case#branch naming
One-click install
npx skills add https://github.com/maarten00/dotfiles --skill create-branch-maarten00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/maarten00/dotfiles/tree/main/skills/create-branch
Command: npx skills add https://github.com/maarten00/dotfiles --skill create-branch-maarten00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent branch naming across repositories makes code history hard to navigate and violates team conventions. This Skill enforces the correct branch naming rules automatically, including the mandatory mku/ prefix for exonet repositories and Conventional Commits prefixes elsewhere. ## Core Features & Use Cases - Remote-aware prefix selection: Inspects the origin remote and applies the mandatory mku/ prefix for github.com/exonet/ repositories, or a Conventional Commits type (feat/, fix/, chore/, refactor/, docs/, test/) for other repositories. - Ticket integration: Includes the EXO-XXXX ticket number right after the prefix when an exonet repository has a Notion or Jira ticket, e.g. mku/EXO-2122-direct-debit-status. - Base branch guidance: Branches off the repository's main branch (master or main) unless told otherwise. - Use Case: When starting work on a bug fix in an exonet repository, the Skill produces a compliant name like mku/EXO-2122-direct-debit-status instead of an ad-hoc branch name. ## Quick Start Create a new branch for my current ticket following the repository's naming conventions.

Frequently Asked Questions about create-branch

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

FAQPage Schema
How do I name a git branch following team conventions?▼

Use the format prefix/short-kebab-case-description. For repositories under github.com/exonet/, the prefix must be mku/; for other repositories, use a Conventional Commits type such as feat/, fix/, chore/, refactor/, docs/, or test/.

How do I include a Jira or Notion ticket number in a branch name?▼

In exonet repositories, place the EXO-XXXX ticket number directly after the mku/ prefix, for example mku/EXO-2122-direct-debit-status. This applies when the work is linked to a Notion or Jira ticket.

What prefix should I use for branches outside exonet repositories?▼

Use a Conventional Commits type as the prefix, such as feat/, fix/, chore/, refactor/, docs/, or test/. Choose the type that best matches the nature of the change being made.

Which branch should I create a new branch from?▼

Branch off the repository's main branch, usually master or main, unless explicitly told otherwise. This keeps new work based on the latest stable state of the codebase.

Can I use my own initials instead of the mku prefix in exonet repos?▼

No. The mku/ prefix is mandatory for all repositories whose origin is under github.com/exonet/. Never substitute another set of initials or a generic prefix in those repositories.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-remote

Manage git remotes and synchronize local branches with remote refs.

Official
Intermediate
werfwerf
4.7k

git-conventions

Generates branch names and commit messages following werf repository conventions.

Official
Intermediate
LedgerHQLedgerHQ
615

git-conventions

Applies repository Git conventions for branch names, commit messages, and pull request titles.

Official
Basic
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced