skills.rest
arbgjr
arbgjrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

auto-branch

Create Git branches with standardized naming conventions and validation.

Updated Jan 15, 2026
Search Tags:#automation#git#workflow#branch#speckit#naming-conventions#hook
One-click install
npx skills add https://github.com/arbgjr/smart_alarm --skill auto-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-branch
Source: https://github.com/arbgjr/smart_alarm/tree/main/.claude/skills/auto-branch
Command: npx skills add https://github.com/arbgjr/smart_alarm --skill auto-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of Git branches following standardized naming conventions to reduce manual errors and speed up setup for new work items.

Core Features & Use Cases

  • Branch naming by type (Bug Fix, Hotfix, Feature, Release, Chore, Refactor, Docs).
  • Hook and CLI integration to trigger branch creation from workflow steps.
  • SpecKit integration to automatically generate branches when new specs are started.

Quick Start

Use the auto-branch hook to create a new feature branch: .claude/hooks/auto-branch.sh feature "Exportacao de Duplicatas"

Frequently Asked Questions about auto-branch

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

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

Automating Git branch creation involves using a hook or CLI integration to generate branches with normalized names based on workflow types like Bug Fix, Hotfix, Feature, Release, Chore, Refactor, and Docs, reducing manual errors.

Can I trigger Git branch generation automatically when a new SpecKit spec starts?▼

Yes, Git branch generation can be triggered automatically when a new SpecKit spec starts through direct SpecKit integration, creating a standardized branch without manual intervention.

What are the limitations when normalizing Git branch names in automated workflows?▼

Branch name normalization enforces a 50-character limit and prohibits special characters, while also checking for existing branches before creation to prevent duplicates and naming conflicts.

How do I create a feature branch using an automated Git hook?▼

You create a feature branch by invoking the auto-branch hook with the branch type and description, such as running the hook script with "feature" and a brief task name to generate a standardized branch.

What Git branch types are supported by automated naming workflows?▼

Automated naming workflows support multiple Git branch types including Bug Fix, Hotfix, Feature, Release, Chore, Refactor, and Docs, ensuring consistent naming across different development tasks.

Do I need to install dependencies to automate Git branch naming?▼

No external dependencies are required to automate Git branch naming, as the skill operates independently using standard Git hooks and SpecKit integration to enforce naming conventions.

Related Skills

Explore More Software Engineering Skills→
qmuqmu
1

manage-branch

Check Git branch state and create timestamped topic branches.

Official
Basic
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
byunghak-dablebyunghak-dable

git-branch

Automate Git branch creation using detected project naming conventions.

Community
Intermediate