git-cherry-pick

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

Updated Mar 13, 2026

Search Tags:#git #pull request #commit #branching #code integration #cherry-pick

Ready to run

npx skills add https://github.com/adamdriscoll/skills --skill git-cherry-pick

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-cherry-pick
Source: https://github.com/adamdriscoll/skills/tree/main/skills/git-cherry-pick
Command: npx skills add https://github.com/adamdriscoll/skills --skill git-cherry-pick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of applying a specific commit from one Git branch to another, streamlining code integration and hotfixes.

Core Features & Use Cases

Selective Commit Transfer: Cherry-pick the latest commit from a source branch to a target branch.
Pull Request Workflow: Optionally create a new branch, cherry-pick onto it, and open a GitHub Pull Request for review.
Use Case: You need to apply a critical bug fix from a develop branch to the main branch without merging the entire develop branch. This Skill can cherry-pick just that one commit.

Quick Start

Cherry-pick the last commit from the 'feature/new-login' branch to the 'main' branch.

Frequently Asked Questions about git-cherry-pick

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

FAQPage Schema

How do I apply a specific commit from one branch to another?▼

Cherry-picking a commit applies a specific commit from a source branch to a target branch using the git cherry-pick command. This selectively transfers changes without merging the entire source branch history.

What is the best way to move a hotfix from a develop branch to main without a full merge?▼

Cherry-picking is the best way to move a hotfix from a develop branch to main without a full merge. It extracts the specific bug fix commit and applies it directly to the target branch, leaving unrelated commits behind.

Can I create a pull request automatically when cherry-picking a commit?▼

Yes, you can create a pull request automatically when cherry-picking a commit by using the optional GitHub CLI workflow. The process creates a new branch, applies the cherry-picked commit, and opens a GitHub Pull Request for review.

Do I need the GitHub CLI to cherry-pick commits between branches?▼

You do not need the GitHub CLI to cherry-pick commits between branches; only Git is required for the core commit transfer. The GitHub CLI is an optional dependency exclusively for automating pull request creation.

When should I use git cherry-pick instead of merging branches?▼

You should use git cherry-pick instead of merging branches when you need to apply a critical bug fix or specific change to a target branch while excluding unrelated commits from the source branch. It is ideal for selective code integration.