Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fritzandfriends/git-workflow
Squad branching model: dev-first workflow with insiders preview channel
Passed 22 of 22 test cases with the skill, and 9 of 22 without it.
and 19 more in the full report
13 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
A critical crash is occurring on `main` in production. What branch prefix should be used for the fix branch, and what is the primary PR target branch?
| Checked | Without skill | With skill |
|---|---|---|
| Prefixes hotfix branch with hotfix/. | Passed | Passed |
| Targets pull request to dev. | Missed | Passed |
The instructions your model reads when the skill loads.
Squad uses a three-branch model. All feature work starts from dev, not main.
| Branch | Purpose | Publishes |
|---|---|---|
main | Released, tagged, in-npm code only | npm publish on tag |
dev | Integration branch — all feature work lands here | npm publish --tag preview on merge |
insiders | Early-access channel — synced from dev | npm publish --tag insiders on sync |
Issue branches MUST use: squad/{issue-number}-{kebab-case-slug}
Examples:
squad/195-fix-version-stamp-bugsquad/42-add-profile-apiBranch from dev:
git checkout dev
git pull origin dev
git checkout -b squad/{issue-number}-{slug}
Mark issue in-progress:
gh issue edit {number} --add-label "status:in-progress"
Create draft PR targeting dev:
gh pr create --base dev --title "{description}" --body "Closes #{issue-number}" --draft
Do the work. Make changes, write tests, commit with issue reference.
Push and mark ready:
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.