mt-create-branch

Name: mt-create-branch
Availability: InStock
Author: t-miura-024

Create a git branch with an auto-generated name from current changes.

Updated May 15, 2026

Search Tags:#git #workflow #feature #branch #hotfix #change analysis

Ready to run

npx skills add https://github.com/t-miura-024/tools --skill mt-create-branch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mt-create-branch
Source: https://github.com/t-miura-024/tools/tree/main/chezmoi/dot_config/opencode/skills/mt-create-branch
Command: npx skills add https://github.com/t-miura-024/tools --skill mt-create-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid manually naming and creating branches by analyzing current changes and generating an appropriate branch workflow.

Core Features & Use Cases

Change-Based Branch Naming: Reviews the current git diff and creates a concise English kebab-case branch name based on the work being done.
Branch Prefix Selection: Automatically chooses hotfix or feature prefixes depending on whether the current branch is main/master or another branch.
Safe Branch Creation: Confirms the proposed branch details before creating and checking out the new branch.

Quick Start

Ask the skill to create a new branch from my current changes and suggest an appropriate branch name.

Frequently Asked Questions about mt-create-branch

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

FAQPage Schema

How do I create a git feature branch from my current uncommitted changes?▼

Creating a git feature branch from current changes requires analyzing the repository diff to generate a descriptive kebab-case name, selecting the correct prefix, and validating branch creation after user confirmation.

How does automatic git branch naming work from a diff?▼

Automatic branch naming from a diff analyzes modified files and code changes to generate a concise English kebab-case name that reflects the specific development work being done.

When do I need a hotfix branch prefix instead of a feature branch prefix?▼

A hotfix branch prefix is automatically selected when the current branch is main or master, while a feature prefix applies when branching from any other development branch.

Can I review the generated branch name before the branch is created?▼

You can review the proposed branch name because the Skill requires explicit user confirmation of the branch details before creating and checking out the new git branch.

What is the best way to organize feature and hotfix branches from existing modifications?▼

Organizing feature and hotfix branches from existing modifications involves analyzing current changes, applying naming conventions with appropriate prefixes, and validating checkout to ensure safe branch creation.