Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →open-gsd/gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review
Passed 10 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
9 fixed5 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/1/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When creating a PR branch after a sprint, which specific directory's commit history should be omitted to keep review diffs focused on source code?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the .planning directory as the target for commit filtering | Missed | Passed |
The instructions your model reads when the skill loads.
$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
This solves the problem of PR diffs being cluttered with PLAN.md, SUMMARY.md, STATE.md changes that are irrelevant to code review.
<execution_context> @~/.claude/gsd-core/workflows/pr-branch.md </execution_context>
test cases passed, vs 4 / 16 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.