What problem does it solve?
Managing dual release lanes (stable on main, beta on next) involves repetitive, error-prone Git operations: syncing branches, repairing release metadata conflicts, re-entering prerelease mode, and verifying npm dist-tags. This Skill automates that entire lane maintenance workflow end-to-end.
Core Features & Use Cases
- Direct main-to-next sync: Merges main into next with a merge commit, automatically repairing known release metadata conflicts (package versions, changelogs, .changeset/pre.json) without creating review-churn PRs.
- Beta promotion and re-entry: Runs the promote workflow to move beta to stable, and restores beta prerelease mode on next after promotion.
- Release verification: Checks GitHub release workflow runs, npm dist-tags for latest and beta, and cleans up stale sync PRs.
- Use Case: After publishing a stable release, invoke this Skill to sync main back into next, regenerate beta changesets, push the merge commit, and confirm npm beta dist-tag points at the expected version.
Quick Start
Ask the agent to run the release-lanes skill in full mode to sync main into next, verify npm dist-tags, and report the final lane state.