Official agent skill

Cherry Pick PR

by kubernetes-sigs in kubernetes-sigs/cloud-provider-azure

Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation.

OfficialApache-2.0Auto-check passedDevelopment

Install Cherry Pick PR

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .claude/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .claude/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .agents/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .agents/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .cursor/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .cursor/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/kubernetes-sigs/cloud-provider-azure.git --path .agents/skills/cherry-pick-pr

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .gemini/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .gemini/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .github/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .github/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install kubernetes-sigs/cloud-provider-azure cherry-pick-pr --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/kubernetes-sigs/cloud-provider-azure.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cherry-pick-pr .opencode/skills/cherry-pick-pr && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cherry-pick-pr" agent skill from https://github.com/kubernetes-sigs/cloud-provider-azure/tree/master/.agents/skills/cherry-pick-pr into .opencode/skills/cherry-pick-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick-pr", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cherry-pick-pr
GitHub stars: 294
Token cost: ~636 tokens
SKILL.md length: 250 words
Files: 2 (incl. scripts)
Skills in repo: 12
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation.

Works in 6 steps: Run a dry-run first → Start the cherry-pick from a clean… → If pick exits with code 3, inspect the… → …
The user wants to backport a PR
SKILL.md covers When To Use, Workflow and Notes
Runs Python scripts from its folder; calls python3, git and gh

What it does

Cherry Pick PR is an agent skill from kubernetes-sigs/cloud-provider-azure, published by the product's own GitHub organization. Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation. Use when the user wants to backport a PR, cherry-pick a commit to a release branch, or mentions cherry-pick, backport, or porting a fix to an older release.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/cherry_pick_pr.py`).

It sits in Development, covering Pull requests. It works with Kubernetes, GitHub and Git. The repository describes itself as: Cloud provider for Azure. The licence is Apache-2.0.

When your agent uses it

The user wants to backport a PR
Cherry-pick a commit to a release branch
Mentions cherry-pick
Porting a fix to an older release

Example prompts

“/cherry-pick-pr”

Requirements

Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Run a dry-run first
Start the cherry-pick from a clean working tree
If pick exits with code 3, inspect the conflicted files from the output,
Run targeted validation after a clean cherry-pick
Create the PR only after test reports success
Abandon a failed or stale attempt with

What it can do on your machine

Read from SKILL.md and the folder at commit 0201852. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cherry Pick PR loads about 636 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 250 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~83
When it runs · the whole SKILL.md, loaded when a task matches: ~636

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from kubernetes-sigs/cloud-provider-azure at commit 0201852, republished under its Apache-2.0 licence (© kubernetes-sigs). 250 words, ~636 tokens.

Download SKILL.mdSave it as .claude/skills/cherry-pick-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: cherry-pick-pr
description: Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation. Use when the user wants to backport a PR, cherry-pick a commit to a release branch, or mentions cherry-pick, backport, or porting a fix to an older release.

Cherry-Pick Pull Requests

When To Use

Use this skill when you need to cherry-pick a merged PR onto a release branch and want the agent to handle the git and GitHub workflow while keeping conflict resolution and test decisions in the loop.

Workflow

Replace <SKILL_DIR> with the path to this skill directory.

Run a dry-run first:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py pick \
  --pr <number> \
  --target-branch <release-X.Y> \
  --dry-run

Start the cherry-pick from a clean working tree:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py pick \
  --pr <number> \
  --target-branch <release-X.Y>

If pick exits with code 3, inspect the conflicted files from the output, read the source diff with gh pr diff <number>, resolve the conflicts, stage the files with git add, then continue:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py continue

Run targeted validation after a clean cherry-pick:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py test

Create the PR only after test reports success:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py create-pr

Abandon a failed or stale attempt with:

bash

python3 <SKILL_DIR>/scripts/cherry_pick_pr.py abort

Notes

The script refuses to start pick from a dirty working tree.
The script refuses to start a new attempt while .git/cherry-pick-pr.json exists. Run abort first.
The state file lives under .git/ intentionally so it stays untracked.
continue runs git cherry-pick --continue non-interactively.
test records passed, failed, or build_failed so the agent can tell the difference between test failures and target-branch compatibility issues.
create-pr reads .github/PULL_REQUEST_TEMPLATE.md at runtime and fails if required anchors drift.
create-pr expects the source PR to already carry a kind/... label. If it does not, fix that first or update the source PR metadata before creating the cherry-pick PR.
Use --chain <branch>... on pick when you want the resulting PR body to append a follow-up /cherrypick ... command for later serialized backports.

Files

SKILL.md and 1 other file (scripts) in .agents/skills/cherry-pick-pr of kubernetes-sigs/cloud-provider-azure.

SKILL.md
scripts/cherry_pick_pr.py

Open the folder on GitHubat commit 0201852

Compare with similar skills

Cherry Pick PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cherry Pick PR compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cherry Pick PR this skillkubernetes-sigs/cloud-provider-azure	294	—	~636	Automated safety check: Pass	Apache-2.0	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	2 days ago
PR Review State Fetchprisma/orm	48k	—	~767	Automated safety check: Pass	Apache-2.0	today
Creating Description For Gh PRredis/jedis	12k	—	~838	Automated safety check: Pass	MIT	today

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
69k GitHub starsUsed in 2 repos~1.1k tokens
DevelopmentAuto-check passed
PR Review State Fetch
prisma/orm
Official
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
48k GitHub stars~767 tokensUpdated today
DevelopmentAuto-check passed
Creating Description For Gh PR
redis/jedis
Official
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
12k GitHub stars~838 tokensUpdated today
DevelopmentAuto-check passed
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
61k GitHub stars~824 tokensUpdated yesterday
DevelopmentAuto-check passed

More from kubernetes-sigs/cloud-provider-azure

All 12 skills in this repo

Run E2E Test
kubernetes-sigs/cloud-provider-azure
Official
Parse a Go e2e test from tests/e2e/, translate each step to kubectl and az CLI commands, and interactively replay the test against a live cluster.
294 GitHub stars~3.8k tokensUpdated yesterday
Auto-check passed
Build Images
kubernetes-sigs/cloud-provider-azure
Official
Build cloud-provider-azure container images through the repo Makefile with explicit IMAGETAG and IMAGEREGISTRY inputs, optional make flag overrides, and opt-in bounded Docker or Podman retries.
294 GitHub stars~1.7k tokensUpdated yesterday
Auto-check passed
Create Release Note Doc PR
kubernetes-sigs/cloud-provider-azure
Official
Generate or update the documentation-site release note for a given tag, commit it on a branch, push it to a writable remote, and open a GitHub PR to the docs branch.
294 GitHub stars~768 tokensUpdated yesterday
Auto-check passed
Create Release Tags
kubernetes-sigs/cloud-provider-azure
Official
Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly…
294 GitHub stars~574 tokensUpdated yesterday
Auto-check passed
Cve Remediator V2
kubernetes-sigs/cloud-provider-azure
Official
Raise Go modules to caller-supplied minimum fixed versions from CVE/GO findings in any format, per tracked module root, sync go.mod/go.sum and root vendor/, audit the source module graphs, run the…
294 GitHub stars~2.5k tokensUpdated yesterday
Auto-check passed
Debug E2E Pipeline
kubernetes-sigs/cloud-provider-azure
Official
Fetch and analyze Prow e2e pipeline failures for cloud-provider-azure.
294 GitHub stars~3.4k tokensUpdated yesterday
Auto-check passed

Works with

Questions about Cherry Pick PR

What does Cherry Pick PR do?

Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation. Cherry Pick PR is an agent skill from kubernetes-sigs/cloud-provider-azure, published by the product's own GitHub organization. Cherry-pick a merged pull request onto a release branch with Prow-style branch naming, manual conflict resolution, targeted validation, and GitHub PR creation.

When should I use Cherry Pick PR?

Cherry Pick PR fits situations like: the user wants to backport a PR; cherry-pick a commit to a release branch; mentions cherry-pick; porting a fix to an older release.

How do I install Cherry Pick PR in Claude Code?

Run `npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a claude-code`. Or copy the skill folder (.agents/skills/cherry-pick-pr in kubernetes-sigs/cloud-provider-azure) into .claude/skills/cherry-pick-pr in your project. Claude Code loads it when a task matches its description.

How do I install Cherry Pick PR in Codex?

Run `npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a codex`. Or copy the skill folder (.agents/skills/cherry-pick-pr in kubernetes-sigs/cloud-provider-azure) into .agents/skills/cherry-pick-pr in your project. Codex loads it when a task matches its description.

Can I use Cherry Pick PR in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kubernetes-sigs/cloud-provider-azure --skill cherry-pick-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cherry-pick-pr, .gemini/skills/cherry-pick-pr, .github/skills/cherry-pick-pr and .opencode/skills/cherry-pick-pr in your project.

What does Cherry Pick PR need to run?

Going by SKILL.md and its folder, Cherry Pick PR needs Python for the scripts in its folder and the command-line tools its instructions call (python3, git and gh). Our summary lists: Python 3.

Does Cherry Pick PR access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cherry Pick PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Cherry Pick PR use?

Cherry Pick PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cherry Pick PR use?

About 636 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cherry Pick PR?

Skills that share tags, products or a category with Cherry Pick PR: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and PR Review State Fetch (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cherry Pick PR?

kubernetes-sigs (a GitHub organization, an official publisher) maintains it in kubernetes-sigs/cloud-provider-azure, which has 294 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.

Source: kubernetes-sigs/cloud-provider-azure on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cherry Pick PR

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Cherry-Pick Pull Requests

When To Use

Workflow

Notes

Files

Compare with similar skills

Similar skills

More from kubernetes-sigs/cloud-provider-azure

Related

Questions about Cherry Pick PR