git-branch

Generate and validate conventional git branch names with type and length constraints.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill git-branch-erclx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-branch
Source: https://github.com/erclx/aitk/tree/main/claude/skills/git-branch
Command: npx skills add https://github.com/erclx/aitk --skill git-branch-erclx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates inconsistent branch naming and prevents the accidental renaming of protected branches or existing remote branches that could break active pull requests.

Core Features & Use Cases

  • Convention Enforcement: Automatically validates branch names against a strict format (type/description) and length limit.
  • Safety Guards: Prevents renaming of protected branches like main or master and checks for remote branch conflicts before execution.
  • Use Case: When starting a new feature, use this skill to ensure your branch name follows team standards and is under the 50-character limit, preventing future merge conflicts or PR issues.

Quick Start

Ask the assistant to generate and apply a conventional branch name based on your current commits.

Frequently Asked Questions about git-branch

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

FAQPage Schema
How do I automate git branch naming conventions for a new feature?

To automate git branch naming, this skill generates and validates conventional branch names based on predefined types and length constraints. It ensures your branch name follows team standards and remains under the 50-character limit to prevent merge conflicts.

Can I prevent accidental renaming of protected git branches like main or master?

Yes, you can prevent accidental renaming of protected branches like main or master. This skill includes safety guards that check for remote branch conflicts and block modifications to protected branches to maintain active pull request integrity.

How do I validate a git branch name against a strict format and length limit?

You validate a git branch name by checking it against a strict type/description format and a 50-character length limit. This skill automatically enforces these repository hygiene constraints before applying any branch name changes to your workflow.

Do I need git CLI access to verify local branch state before renaming?

Yes, you need git CLI access to verify local branch state and remote tracking status. This skill requires CLI access to check for existing remote branches before performing renames, ensuring you do not break active pull requests.

What is the best way to standardize repository hygiene for pull request integrity?

The best way to standardize repository hygiene is to enforce consistent branch naming. This skill standardizes repository hygiene by validating branch names against predefined constraints, preventing naming inconsistencies that could break pull request integrity.