From git-workflows
Always-on branch safety rules: never commit or push directly to main/master, create feature branches with rh/ prefix
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-workflows:branch-safetyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before any commit or push operation, check the current branch. If on `main` or `master`, create a new feature branch first.
Before any commit or push operation, check the current branch. If on main or master, create a new feature branch first.
# Good
git switch -c rh/add-user-auth
git commit -m "feat(auth): add user authentication"
# Bad
git commit -m "feat(auth): add user authentication" # while on main
git push origin main # pushing directly to main
rh/ prefix for new branch namesWhen creating a branch, use the rh/ prefix followed by a short, descriptive kebab-case name.
# Good
rh/add-user-auth
rh/fix-login-redirect
rh/refactor-api-client
# Bad
feature/add-user-auth
add-user-auth
my-branch
If unsure whether to create a new branch or which name to use, ask the user before proceeding. Suggest a default name based on the changes with rh/ prefix.
npx claudepluginhub remihuguet/rems-buddy --plugin git-workflowsCreates 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.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.