How do I install the Git Cherry Pick skill?

Run npx skillmds@latest add majiayu000/git-cherry-pick in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Cherry Pick safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Cherry Pick?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Cherry Pick free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Cherry Pick?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Cherry Pick by majiayu000 — Agent Skill

Name: Git Cherry Pick
Rating: 4.2 (5 reviews)
Author: majiayu000

Git Cherry Pick

This skills takes a source branch and a target branch. It will cherry-pick the last commit from the source branch to the target branch. Optionally, it can also create a pull request for the cherry-picked commit by creating a new branch from the target branch, cherry-picking the commit to that branch, and then creating a pull request from that branch to the target branch using the GitHub CLI.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

git-cherry-pick

Cherry-picks the last commit from a source branch onto a target branch. Supports an optional pull-request workflow that creates an intermediate branch and opens a PR via the GitHub CLI.

Installation

npx skills add adamdriscoll/skills

Git — https://git-scm.com/downloads
GitHub CLI (gh) — https://cli.github.com

Prerequisites

Git must be installed and available in PATH.
GitHub CLI (gh) must be installed and authenticated when using -CreatePullRequest (run gh auth login if needed).

Script

scripts/Invoke-GitCherryPick.ps1

Parameters

Parameter	Type	Required	Description
`SourceBranch`	`string`	Yes	The branch whose last commit will be cherry-picked.
`TargetBranch`	`string`	Yes	The branch to cherry-pick the commit onto.
`PullRequestBranch`	`switch`	No	Creates a new branch from `TargetBranch`, cherry-picks there, and pushes to origin instead of committing directly.
`CreatePullRequest`	`switch`	No	Opens a pull request from the new branch to `TargetBranch` using `gh`. Requires `-PullRequestBranch`.

Usage Examples

Direct cherry-pick onto target branch

.\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main"

Checks out main, pulls the latest changes, and cherry-picks the last commit from feature/my-feature directly onto it.

Cherry-pick via a PR branch (no PR created)

.\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main" -PullRequestBranch

Creates a new branch named cherry-pick/feature/my-feature-to-main, cherry-picks the commit there, and pushes the branch to origin. No pull request is opened.

Cherry-pick and open a pull request

.\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main" -PullRequestBranch -CreatePullRequest

Full workflow: creates the PR branch, cherry-picks the commit, pushes to origin, and calls gh pr create to open a pull request from the new branch to main.

Behavior Notes

The PR branch is automatically named using the pattern cherry-pick/<SourceBranch>-to-<TargetBranch>, with any characters that are invalid in git branch names replaced by -.
If a cherry-pick conflict occurs, the script throws an error. Resolve the conflicts manually and run git cherry-pick --continue to finish.
The script uses git rev-parse on the source branch, so SourceBranch can be any valid git ref (branch name, tag, or commit SHA).

---name: git-cherry-pickdescription: This skills takes a source branch and a target branch. It will cherry-pick the last commit from the source branch to the target branch. Optionally, it can also create a pull request for the cherry-picked commit by creating a new branch from the target branch, cherry-picking the commit to that branch, and then creating a pull request from that branch to the target branch using the GitHub CLI.--- # git-cherry-pick Cherry-picks the last commit from a source branch onto a target branch. Supports an optional pull-request workflow that creates an intermediate branch and opens a PR via the GitHub CLI. ## Installation ```powershell npx skills add adamdriscoll/skills ``` - **Git** — <https://git-scm.com/downloads> - **GitHub CLI (`gh`)** — <https://cli.github.com> ## Prerequisites - **Git** must be installed and available in `PATH`. - **GitHub CLI (`gh`)** must be installed and authenticated when using `-CreatePullRequest` (run `gh auth login` if needed). ## Script `scripts/Invoke-GitCherryPick.ps1` ## Parameters | Parameter | Type | Required | Description | |---|---|---|---| | `SourceBranch` | `string` | Yes | The branch whose **last commit** will be cherry-picked. | | `TargetBranch` | `string` | Yes | The branch to cherry-pick the commit onto. | | `PullRequestBranch` | `switch` | No | Creates a new branch from `TargetBranch`, cherry-picks there, and pushes to origin instead of committing directly. | | `CreatePullRequest` | `switch` | No | Opens a pull request from the new branch to `TargetBranch` using `gh`. Requires `-PullRequestBranch`. | ## Usage Examples ### Direct cherry-pick onto target branch ```powershell .\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main" ``` Checks out `main`, pulls the latest changes, and cherry-picks the last commit from `feature/my-feature` directly onto it. ### Cherry-pick via a PR branch (no PR created) ```powershell .\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main" -PullRequestBranch ``` Creates a new branch named `cherry-pick/feature/my-feature-to-main`, cherry-picks the commit there, and pushes the branch to origin. No pull request is opened. ### Cherry-pick and open a pull request ```powershell .\Invoke-GitCherryPick.ps1 -SourceBranch "feature/my-feature" -TargetBranch "main" -PullRequestBranch -CreatePullRequest ``` Full workflow: creates the PR branch, cherry-picks the commit, pushes to origin, and calls `gh pr create` to open a pull request from the new branch to `main`. ## Behavior Notes - The PR branch is automatically named using the pattern `cherry-pick/<SourceBranch>-to-<TargetBranch>`, with any characters that are invalid in git branch names replaced by `-`. - If a cherry-pick conflict occurs, the script throws an error. Resolve the conflicts manually and run `git cherry-pick --continue` to finish. - The script uses `git rev-parse` on the source branch, so `SourceBranch` can be any valid git ref (branch name, tag, or commit SHA).

Frequently asked questions