skills.rest
sontek
sontekCOMMUNITY
Explore all skills by this author →
Website𝕏@sontekGitHub

create-branch

Validate git branch names against the <type>/<short-description> pattern.

1|1|Updated Jan 6, 2026
Search Tags:#git#workflow#collaboration#coding-standards#branch-naming#feature-branch#branching-conventions
One-click install
npx skills add https://github.com/sontek/agent-skills --skill create-branch-sontek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/sontek/agent-skills/tree/main/plugins/agent-skills/skills/create-branch
Command: npx skills add https://github.com/sontek/agent-skills --skill create-branch-sontek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes git branch naming to improve traceability and collaboration by guiding creation and validation of branch names.

Core Features & Use Cases

  • Branch type guided naming like feat, fix, ref, etc.
  • Validation of <type>/<short-description> pattern and guidance for common branch types
  • Integration with existing git workflows for creating and pushing branches

Quick Start

Create a new feature branch from main: feat/add-user-auth

Frequently Asked Questions about create-branch

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

FAQPage Schema
How do I enforce consistent git branch naming across my development team?▼

Git branch naming conventions improve traceability and collaboration by guiding the creation and validation of branch names using a standardized <type>/<short-description> pattern for all feature, fix, and refactor branches.

What is the standard pattern for creating a feature branch in git?▼

The standard pattern for creating a feature branch is <type>/<short-description>, such as feat/add-user-auth. This format validates that branches include a recognized type prefix and a concise description.

What common git branch type prefixes should I use for fixes and refactors?▼

Common git branch type prefixes include feat for features, fix for bug fixes, and ref for refactoring. These prefixes help categorize the branch purpose within your software development workflow.

How do I validate a git branch name against coding standards before pushing?▼

You validate a git branch name against coding standards by checking it against the <type>/<short-description> pattern, ensuring the branch type is recognized and the description is properly formatted before pushing.

Does this branch naming convention work with existing git collaboration workflows?▼

Yes, this branch naming convention integrates with existing git workflows for creating and pushing branches, applying standardized validation without disrupting your current collaboration processes.

Related Skills

Explore More Software Engineering Skills→
PiklarPiklar

speckit-git-remote

Detect and parse Git remote origin URLs to identify GitHub repository ownership.

Community
Basic
a-taka-tak
1

git-create-pr

Commit changes, push to origin, and create a GitHub Pull Request.

Community
Intermediate
michsindlingermichsindlinger
1

git-workflow-patterns

Guide Git branching strategies, commit message conventions, and pull request workflows.

Community
Basic
iani-kuliiani-kuli

create-branch

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

Community
Intermediate