From git
Creates Git feature branches with short auto-incremented names and type prefixes (feat/fix/refactor/chore/docs). Generates from manual descriptions, uncommitted changes, or Arkhe SDLC specs.
npx claudepluginhub joaquimscosta/arkhe-claude-plugins --plugin gitThis skill uses the workspace's default tool permissions.
Execute feature branch creation with intelligent naming, automatic type detection, and sequential numbering.
Creates git branches following Sentry naming conventions (<username>/<type>/<description>) from arguments, local diffs, or user input. Classifies types like feat/fix/ref/chore. Uses gh CLI for username prefix.
Creates git branches following Sentry naming conventions (<prefix>/<type>/<description>) from args, git diff/status, or generic. Classifies type, picks base, avoids collisions.
Enforces Git branch naming conventions with type prefixes (feat, fix, chore), issue linking, and kebab-case formatting. Use for creating branches, validating names, or setting repository standards.
Share bugs, ideas, or general feedback.
Execute feature branch creation with intelligent naming, automatic type detection, and sequential numbering.
This skill is invoked when:
/create-branch or /git:create-branch commandThe 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
When no arguments provided and no sdlc-develop specs exist, analyze uncommitted changes to generate branch name automatically.
Format: /create-branch (no arguments)
Process:
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)
When no arguments provided and sdlc-develop specs exist, the skill can create branches linked to existing feature specs.
Detection Flow:
.arkhe.yaml exists → read develop.specs_dir (default: arkhe/specs){specs_dir}/ for existing spec directoriesAskUserQuestionExample:
# Specs exist: arkhe/specs/01-user-auth/, arkhe/specs/02-dashboard/
/create-branch
# Prompt: "Select a feature spec for this branch"
# Options: 01-user-auth, 02-dashboard, None (auto-generate from changes)
# User selects 01-user-auth
→ Creates: feat/01-user-auth
The workflow automatically detects commit types from keywords in the description:
| Type | Keywords |
|---|---|
| feat | add, create, implement, new, update, improve |
| fix | fix, bug, resolve, correct, repair |
| refactor | refactor, rename, reorganize |
| chore | remove, delete, clean, cleanup |
| docs | docs, document, documentation |
If no keyword is detected, defaults to feat.
Pattern: {type}/{number}-{keyword1}-{keyword2}
Components:
Examples:
Input: "add user authentication system"
Output: feat/001-user-authentication
Input: "fix null pointer in login"
Output: fix/002-null-pointer
.arkhe.yaml