cherry-pick-pr

To cherry-pick commits without contaminating main, this Skill creates a short-lived branch from your designated base branch, merges main into it, applies the selected commits, and generates a structured pull request. This isolates environment-specific changes from the main branch.

Environment-specific changes leak when feature branches contain commits meant only for branches like qa or staging. This Skill prevents main contamination by routing selected commits through a short-lived branch directly to the target environment branch as an isolated cherry-pick pull request.

The best way to automate a cherry-pick pull request is using a workflow that validates arguments, creates a short-lived branch, merges main, applies the cherry-picked commits, and opens a PR with a structured summary. This Skill performs that integrated workflow for release branches.

Yes, you can isolate qa-specific code by targeting a designated base branch. The Skill creates a short-lived branch, cherry-picks the selected feature branch commits, and generates a pull request to merge them directly into your qa branch, keeping main clean.

No, you do not need to manually merge main. The Skill automatically merges main into the newly created short-lived branch before applying the cherry-picked commits, ensuring the target branch is up to date and reducing integration conflicts.

A key limitation is that the Skill requires valid argument inputs for the target base branch and specific commits. It is designed for environment branches like qa, staging, or release, and relies on a structured pull request workflow rather than direct pushes.