domains / families / software-engineering / create-branch

create-branch

combined

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

When to use

• You need to create a new git branch that follows the repository's naming convention.
• You are starting a new piece of work from the default branch and need help classifying it as `feat`, `fix`, `docs`, or another branch type.
• You want the branch name proposed from either the task description or the current local diff.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

Both copies implement the same Sentry-style branch naming workflow, but they disagree on the branch name format and on how much interaction is allowed. The getsentry/skills copy uses <type>/<short-description> and is explicitly non-interactive, auto-deriving a generic description when there are no local changes and auto-resolving base/collision cases. The sickn33/agentic-awesome-skills copy uses <username>/<type>/<short-description>, requires a username prefix, asks the user when there are no local changes, asks for confirmation before creating, and asks the user to choose a different name on collision. Crowning one copy would hide a real alternative naming convention and interaction model.