skills.rest
diegocanepa
diegocanepaCOMMUNITY
Explore all skills by this author →
GitHub

vcs-branch

Enforce standardized Git branch names with type and issue number.

Updated Feb 18, 2026
Search Tags:#git#workflow#development#branching#vcs#convention
One-click install
npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vcs-branch
Source: https://github.com/diegocanepa/agent-skills/tree/main/skills/vcs-branch
Command: npx skills add https://github.com/diegocanepa/agent-skills --skill vcs-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a consistent and informative Git branch naming convention, improving clarity and organization within development workflows.

Core Features & Use Cases

  • Standardized Naming: Adheres to a <type>/<issue-number>-<short-description> format.
  • Type Categorization: Supports predefined types like feat/, fix/, refactor/, docs/, test/, and chore/.
  • Workflow Integration: Guides users through drafting, user confirmation, and Git execution.
  • Use Case: When starting a new bug fix, you can use this skill to generate a branch name like fix/123-resolve-login-bug.

Quick Start

Draft a new branch name for a feature related to issue 456, with a short description of 'implement user profiles'.

Frequently Asked Questions about vcs-branch

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

FAQPage Schema
How do I standardize Git branch names for feature development and bug fixes?▼

Standardize Git branch names by enforcing a <type>/<issue-number>-<short-description> format. This convention categorizes branches using predefined types like feat, fix, and refactor, while integrating issue numbers to ensure traceability across development workflows.

What is the best way to include issue numbers in Git branch naming conventions?▼

The best way to include issue numbers in Git branch naming conventions is to place them immediately after the branch type, creating a structure like fix/123-resolve-login-bug. This ensures direct traceability between the codebase and project tracking system.

How do I create consistent Git branch names for code refactoring?▼

Create consistent Git branch names for code refactoring by using the refactor type prefix. Following the standardized convention, a refactoring branch would be named refactor/<issue-number>-<short-description>, maintaining clarity and organization within the version control system.

Can I use predefined branch types like chore and docs for my Git workflow?▼

Yes, you can use predefined branch types like chore and docs for your Git workflow. Supported types also include feat, fix, refactor, and test, allowing you to categorize branch names consistently based on the specific development task being performed.

How does standardized branch naming improve version control practices for development teams?▼

Standardized branch naming improves version control practices by providing immediate context about a branch's purpose and associated issue. Enforcing consistent naming conventions across development teams reduces confusion and facilitates smoother code reviews and merging.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
kkhyskkhys
1

creating-branch-name

Generate a kebab-case git branch name from current repository changes.

Community
Intermediate
hiiamskyhiiamsky

git-conventions

Validate Git commit messages, branch names, and PR descriptions against preset conventions.

Community
Intermediate
VidyaBodepudiVidyaBodepudi
2

git-workflow-and-versioning

Guide Git workflows with conventional commits, trunk-based development, and semantic versioning.

Community
Intermediate