branch

Create, switch, list, and delete Git branches with kebab-case naming.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/takapom/trip-app --skill branch-takapom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/takapom/trip-app/tree/main/.claude/skills/branch
Command: npx skills add https://github.com/takapom/trip-app --skill branch-takapom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git ブランチの作成・切り替え・一覧表示・削除を行う。

Core Features & Use Cases

  • ブランチ作成(create)、ブランチ切替(switch)、ブランチ一覧(list)、ブランチ削除(delete)をサポート。
  • チーム開発における命名規則の適用と運用の標準化を支援。

Quick Start

Create a new feature branch from origin/main following the naming convention feature/your-branch

Frequently Asked Questions about branch

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

FAQPage Schema
How do I automate Git branch creation and switching in bash workflows?

Automating Git branch creation and switching in bash workflows is done by executing create and switch operations that enforce naming conventions. This ensures rapid experimentation and clean integration across multiple branches without manual CLI typing.

What is the best way to enforce kebab-case naming conventions for Git branches?

The best way to enforce kebab-case naming conventions for Git branches is by applying automated branch creation rules. This standardizes team development operations and prevents inconsistent branch names from entering the version control workflow.

Can I clean up and delete multiple Git branches from the command line?

You can clean up and delete Git branches from the command line using the delete operation. This removes unwanted branches from your local workflow, maintaining a clean integration environment for active development.

Does this branch management approach work without additional dependencies?

Yes, this branch management approach works without additional dependencies. It operates directly within your existing Git and bash CLI environment, requiring no extra components to create, switch, list, or delete branches.

Why should I use an automated Git branch manager instead of standard CLI commands?

You should use an automated Git branch manager because it standardizes version control operations and enforces naming conventions across your team. Standard CLI commands lack built-in kebab-case validation and require manual workflow consistency.