GI

git.backport

Automates the backporting of git commits to release branches with PR creation.

Install

mkdir -p .claude/skills/git-backport && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11954" && unzip -o skill.zip -d .claude/skills/git-backport && rm skill.zip

Installs to .claude/skills/git-backport

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts, diagnoses the root cause without attempting an autonomous resolution. Use when asked to "backport", "cherry-pick to release", or "port a fix to a release branch".
433 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • →Backport a specific commit from master to a release branch
  • →Create a dedicated backport branch from the target branch
  • →Apply only source file changes from the commit as a patch
  • →Diagnose merge conflicts without autonomous resolution
  • →Open a pull request for the backported changes by default

How it works

The skill creates a new branch from the target, applies the specified commit's source-file changes as a patch, and then pushes the branch to open a PR.

Inputs & outputs

You give it
A commit SHA and a target branch name (e.g., 'f1e04f934715c7a3cb525961dcd5c5c512a83fb2fe32c3293d7e01468be0abcf release-8.x')
You get back
A new backport branch with the cherry-picked commit, a pull request, or a conflict report if the patch fails

When to use git.backport

  • →Backport a bug fix to a release branch
  • →Port a specific commit to a maintenance branch
  • →Automate PR creation for release patches

About git.backport

This skill uses git cherry-pick to port a specific commit from master to a release branch. It creates a dedicated branch, manages the push, and opens a PR by default before returning to the original branch.

Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts, diagnoses the root cause with

When not to use it

  • →When the commit only touches versioning files like package.json or CHANGELOG.md
  • →When autonomous resolution of patch conflicts is required

Limitations

  • →It does not resolve patch conflicts autonomously.
  • →It never applies changes to versioning files like package.json or CHANGELOG.md.
  • →It does not check out the source commit or the target branch locally.

How it compares

This skill automates the cherry-picking process, including branch creation, patch application, and PR opening, while diagnosing conflicts, unlike manual git operations.

Compared to similar skills

git.backport side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
git.backport (this skill)05moReviewIntermediate
resolve-conflicts8112moReviewIntermediate
openspec-onboard109moReviewBeginner
codex-cli-bridge91yReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry