skills.rest
dmzoneill
dmzoneillCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

hotfix

Cherry-pick a commit from a development branch to a release branch.

2|Updated Feb 16, 2026
Search Tags:#git#release management#bug fix#branching#hotfix#cherry-pick
One-click install
npx skills add https://github.com/dmzoneill/skills --skill hotfix-dmzoneill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/dmzoneill/skills/tree/main/hotfix
Command: npx skills add https://github.com/dmzoneill/skills --skill hotfix-dmzoneill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of applying a specific code fix (commit) from a main development branch to an older, active release branch, ensuring critical bug fixes are deployed quickly without disrupting ongoing development.

Core Features & Use Cases

  • Cherry-picking Commits: Safely applies a single commit to a target branch.
  • Branch Management: Handles fetching, checking out, and verifying branches.
  • Tagging & Pushing: Optionally creates a new release tag and pushes changes to the remote repository.
  • Integration: Can comment on Jira issues and log session activity.
  • Use Case: A critical bug is found in production. The fix is committed to main. This Skill cherry-picks that fix to the release/1.2 branch, tags it as v1.2.3, and pushes it to the remote.

Quick Start

Apply the commit 'a1b2c3d4e5f6' to the 'release/1.2' branch and tag it as 'v1.2.3'.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I cherry-pick a commit to a release branch?▼

To cherry-pick a commit to a release branch, this Skill automates fetching, verifying the target branch, applying the specific commit, and optionally pushing the changes. It applies bug fixes to older versions without disrupting ongoing development.

What is the best way to automate applying a hotfix to an older Git branch?▼

Automating a Git hotfix is handled by applying a specific commit from a main development branch to an active release branch. This process safely applies the single commit, tags the new release, and pushes changes to the remote repository.

How do I tag a release and push changes after cherry-picking a bug fix?▼

After cherry-picking a bug fix, this Skill optionally creates a new release tag and pushes the changes to the remote repository. It facilitates the creation of hotfixes by applying bug fixes to older versions.

Does this hotfix process integrate with Jira for issue tracking?▼

Yes, the hotfix process integrates with Jira for issue tracking. It can automatically comment on Jira issues and log session activity while applying commits to designated release branches.

When do I need to cherry-pick a fix instead of merging a branch?▼

You need to cherry-pick a fix when a critical bug is found in production and the fix is committed to a main branch. This applies the specific code fix to an older, active release branch without merging unrelated development work.

Related Skills

Explore More Software Engineering Skills→
berkcangumusisikberkcangumusisik
11

cherry-pick

Locate a commit by description or hash and cherry-pick it into the current branch.

Community
Intermediate
markus41markus41
18

jira:commit

Create Git commits linked to Jira issues with smart commit syntax.

Community
Intermediate
markmhendricksonmarkmhendrickson
27

push

Push the current Git branch to origin with submodule scoping and pre-push checks.

Community
Intermediate
Knuckles-TeamKnuckles-Team
2

git-advanced

Automate Git history fixes using rebase, cherry-pick, and bisect workflows.

Official
Advanced