Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/backport-pr
Backport a merged Next.js pull request from canary to a previous release branch such as next-16-2.
Passed 10 of 15 test cases with the skill, and 7 of 15 without it.
and 3 more in the full report
6 fixed9 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When generating the body markdown for a Next.js backport pull request to next-15-2, what special HTML comment tag must be included at the bottom?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the comment <!-- NEXT_JS_LLM --> in the pull request body. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a user asks to backport a merged Next.js PR to a release branch.
releases/lts/active (the current major's
release line) or releases/lts/maintenance (the previous major's). Only in
exceptionally rare circumstances — a fix for an older minor line that
neither LTS branch supports anymore — is the target a non-LTS branch
(next-<major>-<minor>, which any maintainer can create by pushing a
branch from that line's last tag).Inspect the current worktree before changing branches:
git status --short
git branch --show-current
Preserve unrelated user changes. Do not overwrite, reset, or stash them without the user's consent.
Sync the source and target branches:
git fetch origin canary:refs/remotes/origin/canary <target-branch>:refs/remotes/origin/<target-branch>
Identify the commit that landed the PR on canary:
test cases passed, vs 7 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.