Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
A skill your agent uses when the coordinator dispatches a BACKPORT BRIEF for a single branch.
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers cherry-pick --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .claude/skills/cherry-pick && rm -rf skills-srcUse ~/.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/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .claude/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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 install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pickType 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.
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers cherry-pick --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .agents/skills/cherry-pick && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .agents/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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.
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers cherry-pick --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .cursor/skills/cherry-pick && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .cursor/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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 https://github.com/openshift-eng/ai-helpers.git --path plugins/openshift-developer/skills/cherry-pick--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers cherry-pick --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .gemini/skills/cherry-pick && rm -rf skills-srcUse ~/.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/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .gemini/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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.
$ gh skill install openshift-eng/ai-helpers cherry-pickInstalls 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).
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .github/skills/cherry-pick && rm -rf skills-srcUse ~/.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/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .github/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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.
$ npx skills add openshift-eng/ai-helpers --skill cherry-pick -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers cherry-pick --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/openshift-developer/skills/cherry-pick .opencode/skills/cherry-pick && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cherry-pick" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/openshift-developer/skills/cherry-pick into .opencode/skills/cherry-pick/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-pick", 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.
cherry-pickA skill your agent uses when the coordinator dispatches a BACKPORT BRIEF for a single branch.
Cherry Pick is an agent skill from openshift-eng/ai-helpers. Use when the coordinator dispatches a BACKPORT BRIEF for a single branch. Cherry-picks the named commits onto an OpenShift release branch, resolves conflicts conservatively, runs the repository's checks, and pushes the branch to the bot's fork. Never opens a PR.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitmakeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cherry Pick loads about 579 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 271 words of instructions outside code blocks.
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.
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); files beside SKILL.md are not scanned.
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 271 words, ~579 tokens.
.claude/skills/cherry-pick/SKILL.md (or your agent's skills folder).openshift-developer:cherry-pick
/openshift-developer:cherry-pick <brief><brief>The brief is authoritative: repository, target branch, source commits (in order), head branch name, and the fork remote are all decided by the coordinator's tools. Do not rename, retitle or reorder anything.
git fetch upstream <target_branch> (add upstream for the upstream
repository if the clone's origin is the fork) and
git checkout -b <head_branch> upstream/<target_branch>.git fetch upstream pull/<N>/head covers PR
commits; a squash/merge commit sha is on the base branch). For
source_mode: rebase, find each PR commit's rebased twin on the base
branch by git patch-id and pick those.git cherry-pick -x <sha> for each source commit, in order. Keep the
original authorship and message; the -x trailer is the only addition.vendor/, go.sum, lockfiles
with the project's own commands, never by hand. Never drop or weaken a
test. Consult the conflict_hints PRs (already-resolved newer backports)
for how the same hunk was resolved — but never pick from them. If a
conflict is not mechanically resolvable, stop: push what applies cleanly
in order, report_setback("cherry_pick_conflict", <files and why>), and
end with GOAL_VERDICT: blocked.make build,
make test/make verify, or the language's equivalents). Fix only what
the cherry-pick introduced.git push origin <head_branch>. Do NOT open a PR — the coordinator does,
with the brief's title and body.GOAL_VERDICT: achieved|blocked|failed line.© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/openshift-developer/skills/cherry-pick of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Cherry Pick 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cherry Pick this skillopenshift-eng/ai-helpers | 120 | — | ~579 | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
openshift-eng/ai-helpers
Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file
Works with
Categories
A skill your agent uses when the coordinator dispatches a BACKPORT BRIEF for a single branch. Cherry Pick is an agent skill from openshift-eng/ai-helpers. Use when the coordinator dispatches a BACKPORT BRIEF for a single branch.
Cherry Pick fits situations like: the coordinator dispatches a BACKPORT BRIEF for a single branch.
Run `npx skills add openshift-eng/ai-helpers --skill cherry-pick -a claude-code`. Or copy the skill folder (plugins/openshift-developer/skills/cherry-pick in openshift-eng/ai-helpers) into .claude/skills/cherry-pick in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openshift-eng/ai-helpers --skill cherry-pick -a codex`. Or copy the skill folder (plugins/openshift-developer/skills/cherry-pick in openshift-eng/ai-helpers) into .agents/skills/cherry-pick in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill cherry-pick -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, .gemini/skills/cherry-pick, .github/skills/cherry-pick and .opencode/skills/cherry-pick in your project.
Going by SKILL.md and its folder, Cherry Pick needs the command-line tools its instructions call (git and make).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. Review the folder before installing.
Cherry Pick 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.
About 579 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cherry Pick: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 85k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.
Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.