What formatting rules are applied to branch names?

The skill enforces kebab-case (lowercase with hyphens), limits names to under 50 characters, and removes unnecessary filler words like articles.

Does this skill support ticket numbers?

Yes, the skill includes rules for incorporating ticket numbers (like JIRA IDs) after the prefix for teams that require specific tracking.

Why does it use conventional commit prefixes?

Using prefixes like feat/ or fix/ creates a unified workflow where the branch purpose immediately matches the intended commit type, simplifying automation and reviews.

How does it handle experimental work?

For spikes or uncertain scopes, the skill suggests using 'try-' or 'spike-' prefixes or skipping the standard prefix entirely to denote an experiment.

Conventional Branch Naming

Name: Conventional Branch Naming
Author: poindexter12

bypoindexter12

部署与 DevOps

Generates consistent, descriptive Git branch names aligned with conventional commit standards to streamline repository workflows.

关于

The Branch Naming skill helps developers maintain a clean and professional repository structure by standardizing how Git branches are created. By mapping branch prefixes to conventional commit types—such as feat, fix, and refactor—it ensures a unified workflow from the first checkout to the final merge. The skill enforces best practices like kebab-case formatting, concise naming, and the exclusion of filler words, making it easier for teams to navigate project history and automate CI/CD pipelines.

主要功能

Specialized handling for experimental spikes and trials
0 GitHub stars
Support for ticket numbers and project identifiers
Concise naming logic restricted to 3-5 descriptive words
Conventional commit prefix alignment (feat, fix, docs, etc.)
Automatic kebab-case formatting and lowercase enforcement

使用场景

Automating the transition from task descriptions to Git branches
Standardizing naming conventions across a multi-developer team
Improving repository organization for better audit trails and code reviews

关于

主要功能

Specialized handling for experimental spikes and trials
0 GitHub stars
Support for ticket numbers and project identifiers
Concise naming logic restricted to 3-5 descriptive words
Conventional commit prefix alignment (feat, fix, docs, etc.)
Automatic kebab-case formatting and lowercase enforcement

使用场景

Automating the transition from task descriptions to Git branches
Standardizing naming conventions across a multi-developer team
Improving repository organization for better audit trails and code reviews