What problem does it solve?
Submitting changes in a multi-lane release workflow (dev, minor, major) is error-prone: rebasing onto the wrong base can replay unrelated lane commits, force pushes can overwrite teammates' work, and PRs can end up targeting the wrong base branch. This Skill turns the confirmed output of seed-change-plan into a safe, verified submission.
Core Features & Use Cases
- Safe cross-lane rebase: Uses
git rebase --onto <targetRef> <oldBase> so only your feature commits move between origin/dev, origin/minor, and origin/major, never replaying foreign lane commits.
- Guarded push and PR management: Commits with Conventional Commits messages after user confirmation, pushes with
--force-with-lease pinned to an expected remote SHA, and creates or retargets PRs via gh pr create/gh pr edit --base.
- Post-rebase revalidation: Re-runs the change plan against the new base, executes builds and tests, and verifies PR base/head SHA before reporting.
- Use Case: You finished a feature branched from dev, but the change plan determined it belongs in the minor release lane. The Skill rebases only your commits onto origin/minor, revalidates, force-pushes safely, and updates the PR base to minor.
Quick Start
Ask the assistant to submit the current feature branch according to the confirmed seed-change-plan result, rebasing it onto the planned target branch and creating or updating the GitHub PR.
