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

1. Inspect the current worktree before changing branches: