branch-name
When naming Git branches, provide guidelines on the recommended branch naming conventions for the project.
When & Why to Use This Skill
This Claude skill provides comprehensive guidelines for Git branch naming conventions, ensuring consistency and clarity across software development projects. By enforcing a structured prefix system (such as feat, fix, and refactor) and standardized kebab-case formatting, it helps teams maintain a clean repository history, improves project maintainability, and streamlines the developer workflow.
Use Cases
- Standardizing branch names for new features and bug fixes to improve repository organization and traceability.
- Onboarding new developers by providing immediate, clear instructions on the project's specific naming protocols.
- Ensuring branch names are compatible with CI/CD pipelines that rely on specific prefixes for automated testing and deployment triggers.
- Enhancing collaboration in large teams by making the purpose of every branch immediately identifiable at a glance.
- Linking development work to project management tools by enforcing the inclusion of issue numbers in branch identifiers.
| name | branch-name |
|---|---|
| description | When naming Git branches, provide guidelines on the recommended branch naming conventions for the project. |
Basic Policy
- Prioritize branch names that clearly indicate their purpose at a glance
- Use a structure of prefix +
/+ identifier - Use lowercase and kebab-case for the identifier
- Do not use characters other than alphanumeric and allowed symbols
Prefix List
feat: Add new featuresfix: Fix bugs in existing featureshotfix: Urgent fixes that need immediate deploymentrefactor: Refactoring without changing functionalitychore: Non-functional tasks such as dependency updates and CI configuration adjustmentsdocs: Adding or modifying documentation (not related to functionality)test: Adding or modifying test code (not related to functionality)release: Release preparation tasks
Identifier Naming Rules
- Keep branch names short and meaningful
- Connect words using kebab-case
- Include the issue number at the beginning if the branch is based on an issue
- Write identifiers in English