Routes beta promotion requests to the release-lanes workflow for GitHub release maintenance.
npx skills add https://github.com/udecode/plate --skill promote-beta
Please help me install this Agent Skill. Skill: promote-beta Source: https://github.com/udecode/plate/tree/main/.agents/skills/promote-beta Command: npx skills add https://github.com/udecode/plate --skill promote-beta
Older prompts referencing promote-beta need a compatibility entrypoint that redirects to the current release-lanes workflow, which handles beta promotion, branch sync, and release monitoring as one unified lane.
promote-beta invocations and redirects them to the release-lanes skill for end-to-end beta/latest lane maintenance.gh workflow run promote.yml --ref next -f dry_run=true before any real promotion.main -> next synchronization through tooling/scripts/release-branch-prs.mjs sync-main-to-next with dry-run and push modes.promote-beta; the skill routes them to release-lanes, creates a lane plan scratchpad, and executes a dry-run promotion before the real release.Ask the assistant to run a promote-beta dry run for the next branch and follow the release-lanes workflow for the full promotion.
High-intent search queries and answers about installing and using this skill.
Run a dry run first with gh workflow run promote.yml --ref next -f dry_run=true, then follow the release-lanes workflow for the real promotion. The release-lanes skill handles promotion, branch sync, and npm readback as one lane.
Use the release-branch-prs script: run node tooling/scripts/release-branch-prs.mjs sync-main-to-next --dry-run to preview, then --push to execute. This replaces the old manual generated sync PR step.
promote-beta is a compatibility shim kept so older prompts still route correctly. release-lanes is the current owner, treating promotion, main-to-next sync, beta re-entry, release watching, and stale PR cleanup as one workflow.
No. The skill explicitly instructs not to run the old post-promotion checklist. All non-read-only requests should load the release-lanes rules and follow that workflow instead.
You need the GitHub CLI (gh) to dispatch the promote.yml workflow and Node.js to run the autogoal scratchpad and release-branch-prs scripts. Both are invoked directly from the repository.
beekeeper-labPromote a test branch to main via pull request after tests and lint pass.
Trystan-SABump the version, create a GitHub Release, and publish postkit to npm.
brikkoAIAutomate Brikko Studio release management from branch cutting to publishing.
dotnetStandardizes npm and GitHub releases with semver validation and automation checks.