Stats
Actions
Tags
From git
Git branch naming guidelines. Use when creating, renaming, or checking out new branches.
How this skill is triggered — by the user, by Claude, or both
Slash command
/git: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
Follow the Conventional Branch specification with these details:
Follow the Conventional Branch specification with these details:
Except for main, all branch names must use one of:
feat/: New features (e.g., feat/add-login-page)fix/: Bug fixes (e.g., fix/header-bug)hotfix/: Urgent fixes (e.g., hotfix/security-patch)release/: Release preparation (e.g., release/v1.2.0)chore/: Non-code tasks (e.g., chore/update-dependencies)feat/issue-123-new-login)release/ branchesgit -C <path> when the current directory is already the repository rootnpx claudepluginhub jmfontaine/jmf-claude-plugins --plugin gitCreates 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.
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.
Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.