Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 15 of 20 test cases with the skill, and 8 of 20 without it.
Without skill41%
With skill77%
Checks it passed that the model alone missed
Output executes git diff --stat.
Output executes git log --oneline -5.
Output pipes the log output through tail -80.
and 13 more in the full report
9 fixed8 passed either way4 still failing1 broke
Pass-rate lift
+36 pp
Tokens
+49%
Agent turns
0%
Response time
-48%
Model gemini-3.6-flashMeasured 8/16/2026v117 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I built a new feature adding structured AC editor capabilities. I usually create branches named `feature/structured-ac-editor` or `f/structured-ac-editor`. Give me the exact command to create and switch to the branch following team conventions.
What was checked, without and with the skill
Checked
Without skill
With skill
Output uses the branch prefix feat/ instead of feature/ or f/.