Can I use this for branches without a ticket number?

Yes. While the skill prefers ticket numbers (like eb-1234), it allows for a ticket-less format if you explicitly state there is no ticket associated with the work.

Does it push the new branch to the remote repository automatically?

No, it creates and checks out the branch locally. It then provides the exact git push command for you to run when you are ready to publish the branch.

Does this skill handle git pull before creating a branch?

Yes, the skill automatically switches to the 'dev' branch and pulls the latest changes before creating the new branch to ensure you are building on the most recent code.

What branch types are supported by this skill?

It supports standard types including feature, bugfix, hotfix, release, docs, refactor, test, and chore.

Conventional Git Branch Creator

Name: Conventional Git Branch Creator
Author: finstreet

byfinstreet

•

Herramientas para Desarrolladores

Automates the creation of standardized git branches following the Conventional Branch naming convention.

This skill streamlines the development workflow by ensuring all team members adhere to a consistent git branch naming structure. It automates the multi-step process of switching to the development branch, pulling the latest updates, and creating a new branch formatted with the appropriate type (e.g., feature, bugfix), ticket number, and kebab-case description. By enforcing these standards through Claude, teams can maintain a cleaner, more searchable repository history and reduce manual naming errors.

Características Principales

011 GitHub stars

02Validates formatting to ensure descriptions use proper kebab-case

03Supports multiple branch types including feature, bugfix, hotfix, refactor, and chore

04Prompts for missing information like ticket numbers and descriptions

05Enforces Conventional Branch naming standards: <type>/<ticket>-<description>

06Automates 'git pull' on the dev branch to ensure work starts from the latest code

Casos de Uso

01Quickly spinning up a standardized hotfix branch during production issues

02Ensuring branch name consistency across large engineering teams

03Starting a new feature or task linked to a project management ticket (e.g., Jira/Linear)

Características Principales

011 GitHub stars

02Validates formatting to ensure descriptions use proper kebab-case

03Supports multiple branch types including feature, bugfix, hotfix, refactor, and chore

04Prompts for missing information like ticket numbers and descriptions

05Enforces Conventional Branch naming standards: <type>/<ticket>-<description>

06Automates 'git pull' on the dev branch to ensure work starts from the latest code

Casos de Uso

01Quickly spinning up a standardized hotfix branch during production issues

02Ensuring branch name consistency across large engineering teams

03Starting a new feature or task linked to a project management ticket (e.g., Jira/Linear)