backport-pr
Backport a merged Next.js pull request from canary to a previous release branch such as next-16-2. Use when the user asks to backport, cherry-pick, or open a backport PR from a PR number to an older Next.js version. Covers finding the merged PR commit, creating a backport branch from the target release branch, cherry-picking from canary, validating, and opening the PR with the release branch as the base.
Install
git clone https://github.com/vercel/next.js /tmp/next.js && ln -s /tmp/next.js/.agents/skills/backport-pr ~/.claude/skills/backport-prFrom README
Backport PR Use this skill when a user asks to backport a merged Next.js PR to a release branch. Inputs Require a PR number and a target release branch, for example next-16-2. If the target branch is not provided and cannot be inferred confidently from the user's request, ask before mutating git state. Treat the target branch as variable; do not hard-code next-16-2 except when the user explicitly asks for it. Workflow Inspect the current worktree before changing branches: Preserve unrelated user changes. Do not overwrite, reset, or stash them without the user's consent. Sync the source and target branches: Identify the commit that landed the PR on canary: Prefer mergeCommit.oid when the PR is MERGED and the commit is contained in origin/canary. If GitHub does not return a usable merge commit, use the git log --grep result and verify the commit subject references the PR number.