How do I install the React Sync skill?

Run npx skillmds@latest add vercel-labs/react-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is React Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with React Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is React Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published React Sync?

Vercel Labs (@vercel-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

React Sync by vercel-labs — Agent Skill

Name: React Sync
Author: Vercel Labs

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. Use when working on React changes that need validation in Next.js, or when asked to run buildForNext, pnpm sync-react, or synchronize a React checkout with Next.js.

Vercel Labs 164fda2 2 files · 2.8 KB Updated Sep 17, 2026 28.7k repo stars

File contents

Sync React to Next.js

Use this skill when syncing a local React checkout into this Next.js checkout.

Build and sync

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.

Related Skills

$react-vendoring - vendored React runtime and type boundaries after syncing.

Frequently asked questions