Sync Main To Next
Developmentsync-main-to-nextSync Main To Next is an Agent Skill for development published in the udecode/plate repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
One-command shortcut for syncing origin/main directly into origin/next through release-lanes. Use when the user says sync-main-to-next, asks to sync main into next, asks after a stable release what sync is needed, or wants the fastest safe beta lane catch-up without promotion or broad release-lane ceremony.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/udecode/plate/blob/HEAD/.agents/skills/sync-main-to-next/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sync-main-to-next, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Sync Main To Next
Handle $ARGUMENTS by loading .agents/rules/release-lanes.mdc and running only
its Sync Main To Next lane.
This is a convenience wrapper, not a second release system. release-lanes
owns the release architecture, script contract, hard stops, and handoff shape.
Default Mode
Default to the real sync when the user says sync-main-to-next without
arguments.
Use this sequence:
node tooling/scripts/release-branch-prs.mjs sync-main-to-next --dry-run
node tooling/scripts/release-branch-prs.mjs sync-main-to-next --push
node tooling/scripts/release-branch-prs.mjs verify-main-to-next-sync
Then watch only the workflows created by the pushed sync commit:
gh run list --branch next --limit 10 \
--json databaseId,name,workflowName,headSha,status,conclusion,displayTitle,url
gh run watch <release-run-id> --exit-status
gh run watch <ci-run-id> --exit-status
Read back:
npm view platejs dist-tags --json
npm view platejs@latest version
npm view platejs@beta version
gh release list --limit 5
gh pr list --base next --head sync/main-to-next --state open --json number,url
Close stale sync/main-to-next PRs only after the direct sync and release
verification pass.
Keep It Fast
- Do not create or update a plan unless the user explicitly asks for an autogoal artifact.
- Do not run autoreview.
- Do not create a
main -> nextPR. - Do not touch promotion; this shortcut is not
next -> main. - Do not re-run broad release status commands once the pushed SHA is known.
- Do not wait on unrelated old workflow runs.
Hard Stops
Use the release-lanes hard stops. In practice, stop only for:
- dirty checkout rejected by the direct sync script
- real source conflicts outside known release metadata
- branch protection rejecting the required push
- release or CI failure after one clear repair attempt
- npm/GitHub readback mismatch for the expected
latestorbeta
Handoff
Report in five lines or fewer:
- pushed sync commit
- release and CI run URLs
- npm
latestandbeta - stale PR cleanup result
- residual risk