What is creating-branch?

A Git branch creation workflow that makes feature branches from a description or from uncommitted changes. It names branches using a detected work type such as feature, fix, or refactor, with sequential numbering.

Use it to start work on a task, create a fix or refactor branch, or make a branch name from changes already in progress.

It avoids manually choosing branch names and formats, helping keep branches consistent across a project.

creating-branch — Skill for Claude Code and Codex by joaquimscosta

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add joaquimscosta/arkhe-claude-plugins --skill creating-branch

Clone the repo

git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-plugins

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-branch/github.svg)](https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/creating-branch)

Your own site

<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/creating-branch"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-branch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/creating-branch"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,128 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00111	$0.01128
Opus 5.5	$0.00044	$0.00451
Sonnet 5.5	$0.00022	$0.00226
Haiku 4.5	$0.00011	$0.00113

Measured yesterday against content hash 8ae2a48beb87, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

creating-branch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/git/skills/creating-branch/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Branch Creation Workflow

Execute feature branch creation with intelligent naming, automatic type detection, and sequential numbering.

Usage

This skill is invoked when:

User runs /create-branch or /git:create-branch command
User requests to create a new feature branch
User asks to start a new branch for a task

Two Operation Modes

Mode 1: With Description (Manual)

The command takes a description and automatically detects the commit type.

Format: /create-branch <description>

Examples:

/create-branch add user authentication
→ Creates: feat/001-user-authentication

/create-branch fix login bug
→ Creates: fix/002-login-bug

/create-branch refactor auth service
→ Creates: refactor/003-auth-service

/create-branch remove deprecated code
→ Creates: chore/004-remove-deprecated

/create-branch document api endpoints
→ Creates: docs/005-document-api

Mode 2: Auto-Generate from Changes (No Arguments)

When no arguments provided and no sdlc-develop specs exist, analyze uncommitted changes to generate branch name automatically.

Format: /create-branch (no arguments)

Process:

Check for sdlc-develop specs (see Mode 3)
If no specs, check for uncommitted changes (both staged and unstaged)
If no changes exist, display error and require description
If changes exist, analyze to generate description
Create branch with auto-generated name

Examples:

# After modifying authentication files
/create-branch
→ Auto-detected from changes: feat/006-authentication-system
→ (based on: login.py, auth_service.ts, user_model.py)

# After fixing payment bug
/create-branch
→ Auto-detected from changes: fix/007-payment-processing
→ (based on: payment.js, checkout.py)

Mode 3: From SDLC-Develop Spec (Arkhe Integration)

When no arguments provided and sdlc-develop specs exist, the skill can create branches linked to existing feature specs.

Detection Flow:

Check if .arkhe.yaml exists → read develop.specs_dir (default: arkhe/specs)
Scan {specs_dir}/ for existing spec directories
If specs found → present selection via AskUserQuestion
Use spec directory name for branch name

Read the full file on GitHub · 135 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 135 lines · 111 tokens per session scan A 8ae2a48beb87

Subscribe to this mod's changes

creating-branch is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 111 tokens to every session and 1,128 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.

Git and workflow ai-agents ai-developer-tools anthropic claude-code-agents claude-code-plugins

creating-branch

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Git Branch Creation Workflow

Usage

Two Operation Modes

Mode 1: With Description (Manual)

Mode 2: Auto-Generate from Changes (No Arguments)

Mode 3: From SDLC-Develop Spec (Arkhe Integration)

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

git-workflow

pr-creator

diff-project

finish

dev-finish

dev-rc