cherry-pick

You can cherry-pick a git commit by providing its description. The Skill searches across all branches using git log to locate matching commits, displays the results for selection, and applies the chosen commit to your current branch.

The best way to apply a specific commit is to search by its description or hash. The Skill locates the target commit across your repository, shows the diff, and executes the cherry-pick onto the active branch with success reporting.

Yes, you can review the diff before cherry-picking. The Skill uses git show to display the commit diff, allowing you to verify the correct commit from multiple matches before applying it to your current branch.

Cherry-picking handles conflicts by providing clear failure feedback. When git cherry-pick encounters conflicts, the Skill reports the issue so you can resolve the conflicts manually before continuing with your branch updates.

No, you do not need an exact commit hash to cherry-pick a change. You can locate the target commit by its description, and the Skill will find matching commits across the repository for you to select and apply.

When multiple commits match your search description, the Skill lists all matching results. You can then review the diffs and select the exact commit you need to cherry-pick onto your current branch.