skills.rest
yo-steven
yo-stevenCOMMUNITY
Explore all skills by this author →
GitHub

release-cherry-pick

Cherry-pick labeled merged pull requests from main onto release branches.

Updated May 23, 2026
Search Tags:#release management#github#cherry-pick#branching strategy#merge order#label automation
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill release-cherry-pick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-cherry-pick
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/Model-Optimizer/release-cherry-pick
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill release-cherry-pick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release managers often need to move a specific set of merged, already-reviewed changes from the main branch onto a versioned release branch in a controlled, auditable order.

Core Features & Use Cases

  • Label-driven PR selection: Finds merged PRs on NVIDIA/Model-Optimizer whose base is main and that carry the cherry-pick-<version> label while excluding those already marked cherry-pick-done.
  • Merge-order preservation: Cherry-picks commits one by one in ascending merge date order to reduce dependency and ordering issues.
  • Release-branch PR creation: Pushes the cherry-picks to a dedicated branch and opens a pull request targeting release/<VERSION> with a minimal, PR-number-only checklist-style body.
  • Workflow completion tracking: Adds the cherry-pick-done label to each successfully cherry-picked PR to prevent future reprocessing.

Quick Start

Tell the skill the release version (for example, 0.44.0) and have it open the release branch PR with the cherry-picked changes and label the source PRs as done.

Frequently Asked Questions about release-cherry-pick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cherry-pick merged pull requests into a release branch in merge order?▼

Label-driven cherry-pick automation finds merged PRs carrying a version-scoped label like cherry-pick-<VERSION> while excluding those marked cherry-pick-done, then applies those commits onto the corresponding release branch to move preselected changes from main.

How does label automation select which pull requests to cherry-pick for a release?▼

Label automation selects pull requests by using GitHub search to find merged PRs on main with a cherry-pick-<VERSION> label, excluding any already tagged with cherry-pick-done to prevent future reprocessing of changes already applied to the release branch.

Do I need GitHub CLI access to automate cherry-picking pull requests for a release cut?▼

Yes, GitHub CLI access is required to automate cherry-picking for a release cut. The workflow depends on it to search for labeled merged PRs, retrieve merge commit SHAs, push signed cherry-picks, and open the resulting pull request targeting the release branch.

What happens when a cherry-pick conflict occurs while applying changes to a release branch?▼

When a cherry-pick conflict occurs, the automation prompts the user for conflict resolution. You must manually resolve the conflicts before the process can continue pushing the branch and creating the release pull request with its checklist-style body.

How do I track which pull requests have already been cherry-picked into a release?▼

You track completed pull requests by applying a cherry-pick-done label. After successfully opening a release branch PR, the automation automatically adds this label to each source PR to prevent future reprocessing of the same changes.

Related Skills

Explore More Product & Management Skills→
NVIDIANVIDIA
3.4k

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

Official
Advanced
adamdriscolladamdriscoll

git-cherry-pick

Apply a specific Git commit from a source branch to a target branch.

Community
Intermediate
roanbrasilroanbrasil
5

git-workflow

Implement Git branching strategies, commit discipline, and PR practices.

Community
Advanced
redpanda-dataredpanda-data
12.4k

create-backport-branch

Cherry-pick GitHub PR commits onto a target release branch with git cherry-pick -x.

Official
Advanced