create-branch

Create Git branches with project-defined prefixes and kebab-case names.

Updated Jun 5, 2024
One-click install
npx skills add https://github.com/trysmr/dotfiles --skill create-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/trysmr/dotfiles/tree/main/.claude/skills/create-branch
Command: npx skills add https://github.com/trysmr/dotfiles --skill create-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of new Git branches, ensuring they adhere to your project's specific naming conventions and branching strategy. It eliminates manual errors and saves time, letting you focus on development.

Core Features & Use Cases

  • Automated Branch Naming: Guides the creation of branches (feature/, bugfix/, hotfix/, etc.) following kebab-case and project-defined prefixes.
  • Smart Base Branch Selection: Automatically determines the correct base branch (main or staging) based on your project's configuration and the type of branch being created.
  • Use Case: Before starting a new feature, simply ask the AI to "create a branch for adding user profiles," and it will handle the naming, base branch selection, and creation according to your project's rules.

Quick Start

Create a new branch for a bugfix related to the login error.

Frequently Asked Questions about create-branch

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

FAQPage Schema
How do I automate Git branch creation with naming conventions?

Automated branch creation reads your project's README to determine naming conventions and branching strategy, then constructs kebab-case branch names with prefixes like feature/, bugfix/, or hotfix/ based on the work type, eliminating manual naming errors.

What base branch should I use for different types of Git work?

Branch creation automatically selects the correct base: hotfixes branch from main, feature and bug work branch from staging if present, otherwise main. This ensures consistency with your project's version control workflow.

Can I enforce branch naming rules and policies automatically?

Yes, the Skill enforces naming conventions, validates branches against project rules, applies base-branch policies, and runs branch hooks before creation, ensuring all new branches comply with your standards.

How do I create feature and bugfix branches that follow project conventions?

Specify the work type and description; the Skill reads your project configuration, automatically determines the base branch and prefix, constructs a compliant kebab-case name, and creates the branch with a permission checkpoint.

What happens if my branch doesn't match the project's Git strategy?

The Skill validates branch names and base-branch assignments against your project's README-defined strategy before creation, preventing non-compliant branches and ensuring alignment with your development workflow.

Do I need to manually manage branch prefixes for different work types?

No, the Skill automatically applies the correct prefix—feature/, bugfix/, hotfix/, refactor/, chore/, test/, or tmp/—based on the work type and project configuration, removing manual prefix selection.