create-pr
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.
Install
git clone https://github.com/vercel/next.js /tmp/next.js && ln -s /tmp/next.js/.agents/skills/create-pr ~/.claude/skills/create-prFrom README
Create PR Use this skill when turning local work into a GitHub pull request. Fork PRs vs Branch PRs 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. Workflow Inspect the current state before mutating Git: Stage only files that belong to the requested change. Preserve unrelated user changes. Create or confirm the branch: 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.