Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch.
Passed 11 of 17 test cases with the skill, and 9 of 17 without it.
and 4 more in the full report
6 fixed10 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are ready to stage and commit Group 1 of our split plan on its new branch. What action must be taken immediately before creating the git commit?
| Checked | Without skill | With skill |
|---|---|---|
| invokes commit-rules before committing changes | Missed | Passed |
The instructions your model reads when the skill loads.
Ship an approved split plan so each change group becomes its own reviewable unit, either as a separate branch and PR or as a sequential commit on the current branch.
A split plan must exist in the conversation. The plan specifies an ordered list of groups, each with a name, file list, and any dependencies on earlier groups.
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
Detect the repository state:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'gh pr view)Sample the prevailing workflow from recent default-branch history (git log --first-parent origin/<default-branch> -n 30 --pretty=%s): judge whether changes mostly land through pull requests (merge-PR commits or (#N)-suffixed squash commits) or are committed directly to the default branch.
Output a one-line summary of the detected state as text. Then use request_user_input to choose how to ship the groups:
Recommend the option that fits this repo by listing it first and labeling it (Recommended): a PR-based history recommends separate branches and PRs; a direct-commit history recommends committing each group on the current branch.
If the user declines (chooses the free-form "Other" option or asks to abort), leave the changes staged and do not commit.
Take this step only when the user chose separate branches and PRs.
test cases passed, vs 9 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.