skills.rest
aroido
aroidoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-branch

Generate Git branches following the Conventional Branch specification.

Updated Apr 22, 2026
Search Tags:#git#developer tools#version control#conventional commits#branching
One-click install
npx skills add https://github.com/aroido/vibesmith --skill git-branch-aroido
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-branch
Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/git-branch
Command: npx skills add https://github.com/aroido/vibesmith --skill git-branch-aroido

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git branches, ensuring they adhere to the Conventional Branch specification for better project organization and automated changelog generation.

Core Features & Use Cases

  • Standardized Branch Naming: Enforces a consistent <type>/<description> format.
  • Supported Types: feature, bugfix, hotfix, release, chore.
  • Use Case: When starting a new feature, use this skill to create a branch named feature/user-authentication or when fixing a bug, bugfix/fix-login-error.

Quick Start

Create a new Git branch for a feature called 'implement dark mode'.

Frequently Asked Questions about git-branch

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

FAQPage Schema
How do I create a Git branch following Conventional Commits?▼

Git branch types supported by the Conventional Branch specification include `feature`, `bugfix`, `hotfix`, `release`, and `chore`. Each type dictates a specific `<type>/<description>` naming structure to keep project organization consistent.

How do I automate Git branch creation for a new feature?▼

Automate Git branch creation by guiding the skill to select the appropriate branch type and craft a descriptive name. It then executes the `git checkout -b` command directly, creating branches like `feature/user-authentication` without manual naming errors.

Why use standardized branch naming for version control?▼

Standardized branch naming improves version control by enforcing a consistent `<type>/<description>` format. This clarity supports better project organization and enables automated changelog generation directly from your branch history.

Can I create a hotfix branch using the Conventional Branch specification?▼

Yes, you can create a hotfix branch using the Conventional Branch specification. The skill supports the `hotfix` type, allowing you to generate branches like `hotfix/fix-login-error` through a guided selection and execution process.

What is the best way to name bugfix branches in Git?▼

The best way to name bugfix branches in Git is using the `bugfix/<description>` format. This adheres to the Conventional Branch specification, ensuring strict naming rules for clarity and automated changelog generation.

Related Skills

Explore More Software Engineering Skills→
winsorllcwinsorllc

git-structured

Manage Git repository operations with structured commands and JSON output.

Community
Advanced
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
mhaldermhalder
2

commit

Generate conventional commit messages with type(scope): description format.

Community
Basic
iani-kuliiani-kuli

create-branch

Create git branches with standardized names from user identity and diffs.

Community
Intermediate