Help us improve
Share bugs, ideas, or general feedback.
From feature-lifecycle
Creates a Git feature branch from local main with standard naming. Use when the user wants to create a branch, start a feature branch, check out a new branch for a ticket, or begin work on a Jira issue.
npx claudepluginhub gravity9-tech/claude_code_marketplace_demo --plugin feature-lifecycleHow this skill is triggered — by the user, by Claude, or both
Slash command
/feature-lifecycle:create-branchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a properly named Git feature branch from the local main branch and switch to it.
Creates git branches following Sentry naming conventions (type/short-description). Automatically derives branch description from arguments or git diff, sets base branch, and avoids name collisions.
Creates traceable Git branches for current tasks using ticket IDs or short summaries (e.g., <ticket-id>-<short-kebab-summary>). Inspects git status, safely switches/creates, reports uncommitted work.
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.
Share bugs, ideas, or general feedback.
Create a properly named Git feature branch from the local main branch and switch to it.
The user may provide a ticket key, a description, or both. Parse what's available:
PROJ-123, TEA-42 — an uppercase project prefix, hyphen, and numberIf the ticket key is missing, ask the user with AskUserQuestion:
"What's the Jira ticket key? (e.g., PROJ-123)"
If the description is missing, ask the user with AskUserQuestion:
"Give a short description for the branch (2-4 words, e.g., 'add product rating')"
Format: feature/<ticket-key>-<short-description>
Normalize the description:
a-z, 0-9, hyphens)Examples:
PROJ-42 + "Add Product Search Bar" → feature/PROJ-42-add-product-search-barPROJ-123 + "Fix the cart total bug!!" → feature/PROJ-123-fix-the-cart-totalRun:
git status --porcelain
If there are uncommitted changes, warn the user:
"You have uncommitted changes. These will carry over to the new branch. Continue?"
Use AskUserQuestion with options "Continue" and "Cancel". If cancelled, stop.
Determine whether the local repository uses main or master:
git rev-parse --verify main 2>/dev/null && echo main || echo master
Create the branch from the local default branch (do not fetch or pull from remote):
git checkout -b feature/<ticket-key>-<description> <default-branch>
If the branch name already exists, inform the user and ask if they want to switch to the existing branch or choose a different name.
Report the result:
Branch created: feature/<ticket-key>-<description>
Based on: <default-branch>