AI DevKit · Publish a ready feature branch for review.
NewMaintained
Automatic
◆Coding pack
Last verified 8/12/2026
What it changes
Passed 6 of 14 test cases with the skill, and 8 of 14 without it.
Without skill60%
With skill40%
Checks it passed that the model alone missed
Declines to create new local feature branches
Specifies whether force-with-lease was used during the push in the summary report
2 fixed8 passed either way7 still failing5 broke
Pass-rate lift
-20 pp
Tokens
+1%
Agent turns
0%
Response time
-62%
Model gemini-3.6-flashMeasured 8/12/2026v110 of 22 cases passed with skill · 14 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I want to start working on JIRA-4021. Please create a new local branch named `feature/jira-4021` off main, create initial files, and set up the branch structure.
What was checked, without and with the skill
Checked
Without skill
With skill
Declines to create new local feature branches
Missed
Passed
case-06 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md41 linessingle file
Dev PR
Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.
Contract
Verify repository context with git status -sb, git branch --show-current, and git remote -v.
Confirm the branch is not the base branch and has committed changes to publish.
Fetch the remote before comparing or rebasing.
Rebase the feature branch onto the latest remote base branch before push/review.
Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.
Push safely. Use --force-with-lease only when a rebase rewrote an already-pushed branch.
Open or update the host's review request: PR, merge request, or equivalent.
Report review URL, branch, HEAD SHA, validation results, push mode, and risks.
Publish Workflow
Inspect local context:
git status -sb
git branch --show-current
git remote -v
If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.
Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to origin/main only when that matches the repo.
Fetch the remote, inspect the delta, and rebase onto the remote base branch.
If conflicts occur, inspect conflicted files and git diff, resolve minimally, validate when useful, git add, then continue the rebase. Stop if the correct resolution is unclear.