cherry-pick-backport

AI-assisted cherry-pick backporting resolves merge conflicts by dispatching sub-agents to intelligently adapt code for older API versions and dependencies. It automates conflict resolution during the integration of upstream commits into downstream release branches.

Code adaptation for older Go versions during a cherry-pick is supported by dispatching sub-agents that adjust for dependency differences and API changes. This ensures the backported commit integrates cleanly with the older branch's environment.

Yes, backporting handles detection of upstream and downstream git remotes automatically. It identifies the remote repositories to determine where to pull the original commit from and where to apply the cherry-picked changes.

The best way to verify backported code against the original commit is using the automated review phase, which compares the backported changes against the original and flags unjustified divergences. This ensures the backport maintains the original intent.

Yes, you can optionally push branches and create pull requests after backporting. The Skill supports automated pushing of the isolated worktree branches and subsequent pull request creation to finalize the release management workflow.