Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/create-branch
Create a git branch following Sentry naming conventions.
Passed 5 of 13 test cases with the skill, and 6 of 13 without it.
1 fixed8 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
How do you detect the default branch on origin when git symbolic-ref refs/remotes/origin/HEAD fails?
| Checked | Without skill | With skill |
|---|---|---|
| Falls back to checking local branches main and master using git branch --list main master | Missed | Passed |
| Asks the user for clarification if both or neither main and master exist | Missed | Passed |
The instructions your model reads when the skill loads.
Create a git branch with the correct type prefix and a descriptive name following Sentry conventions.
feat, fix, docs, or another branch type.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.
If $ARGUMENTS is provided, use it as the description of the work.
If no arguments, check for local changes:
git diff
git diff --cached
git status --short
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, different structure |
chore | Deps, config, version bumps, updating existing tooling — no new logic |
test cases passed, vs 6 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.