Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/react-sync
Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.
Passed 22 of 23 test cases with the skill, and 6 of 23 without it.
and 22 more in the full report
16 fixed6 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am inside the Next.js project root trying to sync React. I tried passing `pnpm sync-react ../react` as a positional argument, but it failed. Which specific named CLI flag must be used to supply the React checkout path?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies --version as the required flag for passing the React checkout path. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when syncing a local React checkout into this Next.js checkout.
Build React from its own checkout. Pass this skill's script by its absolute path, because the working directory must be the React repository.
cd <react-repo>
bash <next-repo>/.agents/skills/react-sync/scripts/build-for-next.sh
This creates build/oss-stable and build/oss-experimental with the
bundle variants that Next.js consumes.
Sync the build into Next.js:
cd <next-repo>
PATH="$(dirname "$(command -v corepack)"):$PATH" \
pnpm sync-react --version <react-repo>
Work around a Codex PATH-precedence bug by keeping the directory containing
the active Corepack shim first on PATH. Codex injects a separate bundled
pnpm executable ahead of the user's Corepack shim, and command lookup
happens before Corepack reads the repository's packageManager field. The
prefix makes both this command and sync-react's nested pnpm install
resolve through Corepack to the repository-pinned pnpm version. Invoking
only the outer command with corepack pnpm is insufficient because the
nested command still resolves pnpm from PATH.
Inspect the sync result before testing. Preserve unrelated changes in both checkouts. Rebuild Next.js when required, then run the focused test command matching the changed behavior.
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.