create-branch

Featured

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.

AI & Automation 39,350 stars 6386 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Create Branch Create a git branch with the correct type prefix and a descriptive name following Sentry conventions. ## 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. ## Step 1: Get the Username Prefix Run `gh api user --jq .login` to get the GitHub username. If the command fails (e.g. not authenticated), ask the user for their preferred prefix. ## Step 2: Determine the Branch Description **If `$ARGUMENTS` is provided**, use it as the description of the work. **If no arguments**, check for local changes: ```bash git diff git diff --cached git status --short ``` - **Changes exist**: read the diff content to understand what the work is about and generate a description. - **No changes**: ask the user what they are about to work on. ## Step 3: Classify the Type Pick the type from this table based on the description: | Type | Use when | | --------- | --------------------------------------------------------------------- | | `feat` | New user-facing functionality | | `fix` | Broken behavior now works | | `ref` | Same behavior...

Details

Author
sickn33
Repository
sickn33/antigravity-awesome-skills
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

branch

Creates and switches to a new, conventionally named branch — derives the name from an inline description, conversation context, or local git diffs. Preserves all local changes. Never commits or pushes. Use when you want a properly named branch for new or in-progress work.

57 Updated today
oprogramadorreal
Code & Development Listed

new-branch

Create a strategy-compliant git branch. TRIGGER when the user says "create a branch for X", "start a feature branch", "new fix branch", "cut a release branch", "start a hotfix", "branch for bug in Y", "make a branch named X", "/nyann:branch". DISAMBIGUATION: if the user mentions BOTH branch creation AND committing in the same message (e.g. "branch and commit", "start a branch and commit this"), this skill wins — create the branch first, then suggest `/nyann:commit` (or the commit skill) as the follow-up. Do NOT trigger on informational questions about branches ("what branch am I on?") or on general git-history questions.

5 Updated yesterday
thettwe
Code & Development Solid

create-pr

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

27,705 Updated today
davila7
AI & Automation Listed

managing-branches

Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.

335 Updated today
aiskillstore
Code & Development Listed

create-pr

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

335 Updated today
aiskillstore