backport

Automate merged GitHub pull request backporting to release or devnet staging branches.

Updated May 14, 2026

Search Tags:#git #pull request #worktree #conflict resolution #GitHub CLI #backport #release branches

Ready to run

npx skills add https://github.com/HabibTorjmen/Blockchain --skill backport-habibtorjmen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backport
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/backport
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill backport-habibtorjmen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, yarn, bootstrap.sh, and includes scripts (resource) components.

What problem does it solve?

Backporting merged pull requests to a specific release or devnet staging branch can be slow and error-prone, especially when the target branch has diverged and patch hunks no longer apply cleanly.

Core Features & Use Cases

Automated backport to staging: Uses an existing backport script for the happy path to move a merged PR into a staging-area branch.
Conflict-aware manual resolution: Detects failed hunks via reject files, lets you adapt changes to the release branch state, and resumes through the script workflow.
Safety checks before work: Verifies the PR is merged, validates argument structure, and prevents duplicate backports by checking staging commit history.

Quick Start

Backport PR 12345 to the v4 release staging area by running: /backport 12345 v4

Frequently Asked Questions about backport

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

FAQPage Schema

How do I backport a merged pull request to a release staging branch?▼

To backport a merged pull request, you can automate the process by running a backport script that moves the PR into a staging branch, such as v4, using an isolated git worktree to apply the changes safely.

What happens if a backported PR has merge conflicts in the release branch?▼

When a backported PR has conflicts, the workflow detects failed hunks via reject files, allowing you to manually adapt the changes to the release branch state and resume the script workflow using conflict continuation.

Do I need the GitHub CLI to backport pull requests to devnet branches?▼

Yes, you need the GitHub CLI (gh) installed to backport pull requests to devnet branches, as the workflow requires validating the PR state and checking staging commit history to prevent duplicate backports.

Can I verify a backported PR compilation without running full CI tests?▼

Yes, after resolving any conflicts and reject hunks in the isolated git worktree, the backport workflow verifies build compilation directly without running the full CI test suite.

How does using a git worktree help when backporting to staging?▼

Using a git worktree during a backport creates an isolated environment for the target release branch, preventing disruption to your local repository state while you apply diffs and resolve any reject hunks.