create-backport-branch

To backport a pull request, you cherry-pick all commits from the source PR onto a target release branch. This Skill automates that process by creating a dedicated branch and applying the changes using git cherry-pick -x to maintain a traceable record.

The safest way to cherry-pick commits is using an automated workflow with built-in guardrails. This Skill applies commits with git cherry-pick -x and safely aborts on uncertain conflicts, reporting outcomes like skipped files or touched files to prevent error-prone manual merges.

To start cherry-picking, provide the TARGET release branch or commit and the PR_NUM. The system uses these two arguments to automatically create a backport branch with an ai-backport- prefix and applies the changes from the specified PR.

Yes, you can use git cherry-pick to backport multiple commits from a single PR. The Skill automatically cherry-picks all commits from the provided PR number onto the target branch, tracking progress and reporting detailed outcomes for each commit.

When a cherry-pick encounters a conflict during a PR backport, the process safely aborts to avoid uncertain merges. The Skill reports the conflict outcomes, including any skipped or touched files, leaving the repository in a safe state for manual resolution.

An automated backport branch prevents error-prone manual workflows by creating a traceable branch name with the ai-backport- prefix. It applies git cherry-pick -x to record source commits, ensuring stable bugfixes and clear identification of the backport scope and origin PR.