Automated summary
This skill manages Git branches: create, switch, list, and delete, following a structured naming convention.
Strengths
- Enforces a clear and consistent naming convention
- Provides safe operations (state checks, confirmation before deletion)
- Fetches latest origin/main to base new branches on
Limitations
- Does not handle complex operations like rebase or merge
- The naming convention is hardcoded and not customizable
- Relies on local Git configuration
Use this skill to streamline and standardize branch management in a typical Git workflow.
Avoid using it when you need advanced operations (interactive rebase, cherry-pick) or if your team uses a different naming convention.
Security analysis
SafeThe skill uses standard git commands for branch management. It does not pull in external scripts, exfiltrate data, or disable safety features. It includes guidelines to confirm before destructive actions like branch deletion with confirmation checks for uncommitted changes.
No concerns found
How this analysis is madeExamples
Create a new branch for the login feature, based on origin/main.Switch to the branch fix/login-error.Delete the local branch chore/update-deps after it has been merged.name: branch description: gitブランチの作成・切り替え・一覧・削除を行う。「ブランチ作って」「ブランチ切り替えて」「ブランチ整理して」などのリクエストで使用する。 allowed-tools: Bash argument-hint: [create|switch|list|delete] [ブランチ名]
Git ブランチ管理
フィーチャーブランチの作成、切り替え、一覧表示、削除を行う。
ブランチ命名規則
<type>/<短い説明（英語ケバブケース）>
type 一覧
| type | 用途 | 例 |
|---|---|---|
| feature | 新機能開発 | feature/auth-screen |
| fix | バグ修正 | fix/login-error |
| refactor | リファクタリング | refactor/hiroba-api |
| chore | 設定・ツール変更 | chore/update-deps |
| docs | ドキュメント | docs/api-guide |
| ui | UI/デザイン変更 | ui/home-screen-redesign |
操作一覧
ブランチ作成（create）
# 現在のブランチの最新状態から作成
git checkout -b <type>/<名前>
# リモートの main から作成（推奨）
git fetch origin && git checkout -b <type>/<名前> origin/main
ブランチ切り替え（switch）
# ローカルブランチに切り替え
git switch <ブランチ名>
# 未コミットの変更がある場合は stash してから切り替え
git stash && git switch <ブランチ名>
ブランチ一覧（list）
# ローカルブランチ一覧
git branch -v
# リモートを含む全ブランチ
git branch -av
ブランチ削除（delete）
# マージ済みブランチを削除
git branch -d <ブランチ名>
# リモートブランチも削除
git push origin --delete <ブランチ名>
手順
- 引数から操作タイプ（create / switch / list / delete）を判定する
- 引数にブランチ名やキーワードがあれば命名規則に従ってブランチ名を生成する
git statusで未コミットの変更がないか確認する- 未コミットの変更がある場合はユーザーに対応方法を確認する（コミット / stash / 破棄）
- 操作を実行する
ルール
mainブランチへの直接コミットは推奨しない。作業はフィーチャーブランチで行う- ブランチ作成時は
origin/mainの最新を取得してから分岐する - ブランチ削除前にマージ状態を確認する
git branch -D（強制削除）は明示的に指示された場合のみ使用する- ブランチ名は英語のケバブケースで統一する
- 切り替え前に未コミットの変更を必ず確認する
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/git-branch-management-mma3jrig/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/git-branch-management-mma3jrig' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-branch-management-mma3jrig/download' --output '.skill-downloads/git-branch-management-mma3jrig/SKILL.md.part' && mv '.skill-downloads/git-branch-management-mma3jrig/SKILL.md.part' '.skill-downloads/git-branch-management-mma3jrig/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/git-branch-management-mma3jrig/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.