branch

Create Git branches with repository-specific naming conventions and ticket IDs.

3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/nmoinvaz/speedy-gonzales --skill branch-nmoinvaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/nmoinvaz/speedy-gonzales/tree/main/skills/branch-name
Command: npx skills add https://github.com/nmoinvaz/speedy-gonzales --skill branch-nmoinvaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of Git branches, ensuring they adhere to established naming conventions within a repository, streamlining the branching process.

Core Features & Use Cases

  • Automated Branch Naming: Generates branch names based on detected repository patterns and user-provided context.
  • Intelligent Convention Detection: Analyzes existing branches to infer common naming structures (e.g., feature/TICKET-123-description).
  • Ticket ID Integration: Searches conversation history and staged changes for ticket IDs to incorporate into branch names.
  • Bug Fix Branch Suffixing: Automatically adds incremental suffixes to bug fix branches to prevent naming conflicts.
  • Use Case: When starting a new feature, you can ask the skill to create a branch named feature/PROJ-456-add-user-auth, and it will handle the naming and creation for you.

Quick Start

Create a new git branch for a feature, incorporating the ticket ID PROJ-789 and the description 'implement dark mode'.

Frequently Asked Questions about branch

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

FAQPage Schema
How do I create a git branch that automatically follows repository naming conventions?

To create a git branch with naming conventions, this skill analyzes existing branches to infer patterns like feature/TICKET-ID-description and generates the new branch name accordingly. It automates the naming and creation process to ensure adherence to repository standards.

Can I automatically extract a ticket ID from staged changes for my branch name?

Yes, you can extract a ticket ID from staged changes. The skill intelligently searches conversation history and staged changes for ticket IDs, incorporating them directly into the generated branch name to maintain consistent tracking.

What is the best way to prevent naming conflicts when creating multiple bugfix branches?

The best way to prevent naming conflicts for bugfix branches is using incremental suffixing. The skill automatically adds incremental suffixes to bug fix branches, ensuring unique names and avoiding collisions when multiple fixes are developed concurrently.

Does this git branch creation tool work without needing additional dependencies installed?

Yes, the git branch creation tool works without needing additional dependencies installed. It operates independently with no required dependencies, allowing you to generate and create branches with naming conventions directly within your development environment.

How do I generate a feature branch name using a specific ticket number and description?

To generate a feature branch name, provide the ticket number and description in your prompt. The skill uses this context to create a branch formatted as feature/TICKET-ID-description, such as feature/PROJ-789-implement-dark-mode, handling the creation for you.