How do I install the Backport Pr Assistant skill?

Run npx skillmds add majiayu000/backport-pr-assistant in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backport Pr Assistant safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backport Pr Assistant?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backport Pr Assistant free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backport Pr Assistant?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backport Pr Assistant by majiayu000

Name: Backport Pr Assistant
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

CockroachDB Backport Assistant

Help the user backport pull requests to older release branches, especially when conflicts need resolution.

Backport CLI Tool Reference

Basic Usage:

backport <pull-request>...              # Backport entire PR(s)
backport <pr> -r <release>              # Target specific release (e.g., -r 23.2)
backport <pr> -b <branch>               # Target specific branch (e.g., -b release-23.1.10-rc)
backport <pr> -j "justification"        # Add release justification
backport <pr> -c <commit> -c <commit>   # Cherry-pick specific commits only
backport <pr> -f                        # Force operation

Conflict Resolution:

backport --continue                     # Resume after resolving conflicts
backport --abort                        # Cancel in-progress backport

Common Examples:

backport 23437                          # Simple backport
backport 23437 -r 23.2                  # To release-23.2 branch
backport 23437 -j "test-only changes"   # With justification
backport 23437 -b release-23.1.10-rc    # To specific release candidate branch

Workflow

Start the backport: Run backport <pr> -r <release> for the target branch
When conflicts occur: The tool stops and lists conflicting files
Analyze conflicts: Read the conflicting files, understand what's different between branches
Resolve conflicts: Edit files to resolve, then git add the resolved files
Continue: Run backport --continue to resume
Repeat if more conflicts arise
Complete: The backport tool pushes and creates the PR (do not use gh CLI to make the PR)

Conflict Resolution Guidelines

Simple conflicts you can resolve directly:

Import statement conflicts
Simple variable name changes
Basic formatting differences
Minor API signature changes that are obvious

Complex conflicts - ask the user for guidance:

Conflicts involving significant logic changes
Dependencies that don't exist in the target branch
API changes requiring substantial modification
Multiple conflicting files with interdependent changes
Changes that may not be appropriate for the target branch

When Resolving Conflicts

Explain what's conflicting - show the relevant code sections
Explain why - what's different between branches that caused this
Propose a resolution - or ask for guidance if complex
After resolving: git add <files> then backport --continue

---name: backport-pr-assistantdescription: Help backport PRs to release branches using the backport CLI tool. Use when backporting changes that have merge conflicts requiring manual resolution.--- # CockroachDB Backport Assistant Help the user backport pull requests to older release branches, especially when conflicts need resolution. ## Backport CLI Tool Reference **Basic Usage:** ```bash backport <pull-request>... # Backport entire PR(s) backport <pr> -r <release> # Target specific release (e.g., -r 23.2) backport <pr> -b <branch> # Target specific branch (e.g., -b release-23.1.10-rc) backport <pr> -j "justification" # Add release justification backport <pr> -c <commit> -c <commit> # Cherry-pick specific commits only backport <pr> -f # Force operation ``` **Conflict Resolution:** ```bash backport --continue # Resume after resolving conflicts backport --abort # Cancel in-progress backport ``` **Common Examples:** ```bash backport 23437 # Simple backport backport 23437 -r 23.2 # To release-23.2 branch backport 23437 -j "test-only changes" # With justification backport 23437 -b release-23.1.10-rc # To specific release candidate branch ``` ## Workflow 1. **Start the backport**: Run `backport <pr> -r <release>` for the target branch 2. **When conflicts occur**: The tool stops and lists conflicting files 3. **Analyze conflicts**: Read the conflicting files, understand what's different between branches 4. **Resolve conflicts**: Edit files to resolve, then `git add` the resolved files 5. **Continue**: Run `backport --continue` to resume 6. **Repeat** if more conflicts arise 7. **Complete**: The backport tool pushes and creates the PR (do not use `gh` CLI to make the PR) ## Conflict Resolution Guidelines **Simple conflicts you can resolve directly:** - Import statement conflicts - Simple variable name changes - Basic formatting differences - Minor API signature changes that are obvious **Complex conflicts - ask the user for guidance:** - Conflicts involving significant logic changes - Dependencies that don't exist in the target branch - API changes requiring substantial modification - Multiple conflicting files with interdependent changes - Changes that may not be appropriate for the target branch ## When Resolving Conflicts 1. **Explain what's conflicting** - show the relevant code sections 2. **Explain why** - what's different between branches that caused this 3. **Propose a resolution** - or ask for guidance if complex 4. **After resolving**: `git add <files>` then `backport --continue`

Frequently asked questions