Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/create-pr
Create Git branches, commits, pushes, and GitHub pull requests for Next.js.
Passed 9 of 15 test cases with the skill, and 7 of 15 without it.
and 8 more in the full report
8 fixed7 passed either way5 still failing5 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.8-flash on 10/18/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.
After staging packages/next/src/server/base-server.ts with git add, what check command should be run to verify whitespace and conflict markers before running git commit?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies git diff --cached --check. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when turning local work into a GitHub pull request.
Before writing a PR description, check whether this is a branch PR (the
branch lives in vercel/next.js) or a fork PR (an external contribution from
a fork). You may write full descriptions for branch PRs, but not for fork
PRs — inform the user, offer to review their description or provide technical
details, and give them the GitHub URL to create the PR themselves. See
"GitHub Pull Requests and Issues" in AGENTS.md for the full policy.
Inspect the current state before mutating Git:
git status --short
git branch --show-current
git diff -- <paths>
Stage only files that belong to the requested change. Preserve unrelated user changes.
Create or confirm the branch:
git switch -c <agent-name>/<short-topic>
Prefix the branch with your agent's name as a single lowercase word, such
as codex/, claude/, or fleet/ (e.g. claude/<short-topic>), unless
the user asks for a different name. If a
.git/*lock or Operation not permitted error appears, rerun the same Git
command with sandbox escalation. Do not assume a branch namespace conflict
until checking refs with git branch --list, git show-ref, or
git for-each-ref.
test cases passed, vs 7 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.