release-cherry-pick
CommunityCherry-pick labeled PRs into a release
Product & Management#release management#github#cherry-pick#branching strategy#merge order#label automation
Authoryo-steven
Version1.0.0
Installs0
System Documentation
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 markedcherry-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-donelabel 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.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: release-cherry-pick Download link: https://github.com/yo-steven/skills-exploration-20260522/archive/main.zip#release-cherry-pick Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.