Setting the skill. One moment.
24 skills · 112 min
Skills
Skill 3 of 24
Create Git branches, commits, pushes, and GitHub pull requests for Next.js.
2 minutes · 407 words · 5 sections
Install
npx skills add vercel/next.js --skill create-prnpx skills add vercel/next.js/plugin marketplace add vercel/next.jsThe first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.
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 codex/<short-topic>Use the codex/ prefix 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.
Validate and commit:
git
Use this PR body format:
## Summary
<what changed and why>
## Verification
- `<command that passed>`
- Not run: `<command>` (`<reason>`)
<!-- NEXT_JS_LLM -->The “what” should be explained from the end-user perspective or developer perspective. Only include implementation changes if they’re not obvious from the diff.
A “why” should be included if the change isn’t self-explanatory, or if the motivation is not clear from the diff. Omitting the “why” should be used sparingly and only for small changes.
Do not include trivial verification commands that CI already covers (e.g. pnpm run build), but do include any manual verification steps. If the PR changes a test, you don’t need to repeat the command to run that test. But if you used an existing test to validate some behavior didn’t change, include that test.
Use --body with this filled content.
If a PR may already exist, check before creating a duplicate:
gh pr view --head <branch> --json url,isDraft,titleIf approval is denied for gh pr create, report that the branch is pushed
but the PR was not created, and provide the exact corrected command.
After successful Codex app Git actions, include the appropriate final-response directives for branch creation, staging, committing, pushing, and PR creation.
$pr-status-triage - Analyze CI failures and PR review feedback after the PR exists.$gh-stack - Manage stacked branches and dependent pull requests.Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull_request_template.md, --body formatting, codex/ branch names, and Codex app git directives.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
canary, last pushed 28 August 2026.SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .agents/skills/*/SKILL.md, skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Vercel, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.Keep commit messages concise and do not add generated-tool or co-author footers.
Push the branch:
git push -u origin <branch>Create the PR as a draft unless the user explicitly asks otherwise:
gh pr create --draft --base canary --head <branch> --title "<title>" --body '<body>'For this repo, prefer canary as the base branch. If GitHub network access
fails in the sandbox, rerun with escalation.
/vercel/next.js.md, and each skill at its own .md URL.