New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Backport

by GoogleCloudPlatform in GoogleCloudPlatform/spring-cloud-gcp

Backports pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x).

Apache-2.0Auto-check passedDevelopment

Install Backport

skills CLI
$ npx skills add GoogleCloudPlatform/spring-cloud-gcp --skill backport -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install GoogleCloudPlatform/spring-cloud-gcp backport --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/spring-cloud-gcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backport .claude/skills/backport && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
backport
GitHub stars
554
Token cost
~862 tokens
SKILL.md length
353 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Backports pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x).

  • Works in 6 steps: Identify Commit Hash → Fetch Upstream State → Create Tracking Branch → …
  • Instructed to cherry-pick
  • SKILL.md covers Prerequisites, Branching & Naming Conventions, Pull Request Metadata… and Step-by-Step Execution Workflow, plus 1 more section
  • Calls git and gh

What it does

Backport is an agent skill from GoogleCloudPlatform/spring-cloud-gcp. Backports pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x). Use when instructed to cherry-pick, backport, or migrate merged pull requests or commits to older support branches in the repository.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with Google Cloud and GitHub. The repository describes itself as: New home for Spring Cloud GCP development starting with version 2.0. The licence is Apache-2.0.

When your agent uses it

  • Instructed to cherry-pick
  • Migrate merged pull requests
  • Commits to older support branches in the repository

Example prompts

  • “Use the backport skill to backport pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x)”
  • “/backport”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Identify Commit Hash
  2. Fetch Upstream State
  3. Create Tracking Branch
  4. Cherry-Pick Commit
  5. Push Branch to Upstream
  6. Create Pull Request

What it can do on your machine

Read from SKILL.md and the folder at commit 8eaa34d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Backport loads about 862 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 353 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~862

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from GoogleCloudPlatform/spring-cloud-gcp at commit 8eaa34d, republished under its Apache-2.0 licence (© GoogleCloudPlatform). 353 words, ~862 tokens.

Download SKILL.mdSave it as .claude/skills/backport/SKILL.md (or your agent's skills folder).
name
backport
description
Backports pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x). Use when instructed to cherry-pick, backport, or migrate merged pull requests or commits to older support branches in the repository.

Backporting Pull Requests

This document defines the standard operating procedures and conventions for AI agents performing backporting tasks in the spring-cloud-gcp repository.

Prerequisites

  • Access to the git command line tool.
  • Access to the GitHub CLI (gh), authenticated with sufficient repository scopes to create branches and pull requests.

Branching & Naming Conventions

  • Target Release Branches: Active support branches such as 6.x and 7.x.
  • Local/Head Branch Name: <target-branch>-cherry-pick-<short-commit-hash>
    • Example: 6.x-cherry-pick-366c6fe (where 366c6fe is the 7-character short hash of the commit from main).

Pull Request Metadata Conventions

To ensure consistency and traceability across releases, backport pull requests MUST adhere to the following formatting rules:

  • PR Base: The target release branch (e.g., 6.x).
  • PR Title: Must EXACTLY match the original PR title from main, including the original PR number suffix.
    • Example: fix: NullPointerException in spring-cloud-gcp-data-spanner (#4383)
  • PR Body: Must contain exactly the string backport followed by the full GitHub URL of the original pull request.
    • Example: backport https://github.com/GoogleCloudPlatform/spring-cloud-gcp/pull/4383

Step-by-Step Execution Workflow

When instructed by a user to backport one or more PRs, follow this exact sequence for each PR and target branch combination:

Step 1: Identify Commit Hash

Find the commit hash of the merged PR on the main branch.

bash
git log --oneline origin/main
Step 2: Fetch Upstream State

Ensure local tracking branches are up to date.

bash
git fetch origin
Show full SKILL.md (145 more words)Show less
Step 3: Create Tracking Branch

Checkout a new branch from the target release branch.

bash
git checkout -b <target-branch>-cherry-pick-<short-hash> origin/<target-branch>
Step 4: Cherry-Pick Commit

Cherry-pick the commit from main.

bash
git cherry-pick <full-commit-hash>

Note: If merge conflicts arise, resolve them according to the target branch's baseline dependencies and continue the cherry-pick.

Step 5: Push Branch to Upstream

Push the newly created branch to the remote repository.

bash
git push origin <target-branch>-cherry-pick-<short-hash>
Step 6: Create Pull Request

Create the pull request via GitHub CLI (gh), specifying the target base branch, exact title, and body.

bash
gh pr create \
  --base <target-branch> \
  --title "<original-pr-title> (#<original-pr-number>)" \
  --body "backport https://github.com/GoogleCloudPlatform/spring-cloud-gcp/pull/<original-pr-number>"

Important Operating Principles

  1. Atomic Backports: Always backport each pull request individually. Do not combine multiple PRs into a single cherry-pick branch or backport PR unless explicitly instructed by the user.
  2. Author Attribution: Git cherry-pick preserves the original commit authorship automatically. Do not alter the commit author during the process.
  3. Verification: Verify that the PR was successfully created and verify the CI checks once opened.

© GoogleCloudPlatform, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/backport of GoogleCloudPlatform/spring-cloud-gcp.

Open the folder on GitHubat commit 8eaa34d

Compare with similar skills

Backport next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Backport compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Backport this skillGoogleCloudPlatform/spring-cloud-gcp554—~862Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

Works with

Categories

Questions about Backport

What does Backport do?

Backports pull requests that have been merged into the main branch across to older active release branches (e.g., 6.x, 7.x). Backport is an agent skill from GoogleCloudPlatform/spring-cloud-gcp.x).

When should I use Backport?

Backport fits situations like: instructed to cherry-pick; migrate merged pull requests; commits to older support branches in the repository.

How do I install Backport in Claude Code?

Run `npx skills add GoogleCloudPlatform/spring-cloud-gcp --skill backport -a claude-code`. Or copy the skill folder (.agents/skills/backport in GoogleCloudPlatform/spring-cloud-gcp) into .claude/skills/backport in your project. Claude Code loads it when a task matches its description.

How do I install Backport in Codex?

Run `npx skills add GoogleCloudPlatform/spring-cloud-gcp --skill backport -a codex`. Or copy the skill folder (.agents/skills/backport in GoogleCloudPlatform/spring-cloud-gcp) into .agents/skills/backport in your project. Codex loads it when a task matches its description.

Can I use Backport in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GoogleCloudPlatform/spring-cloud-gcp --skill backport -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backport, .gemini/skills/backport, .github/skills/backport and .opencode/skills/backport in your project.

What does Backport need to run?

Going by SKILL.md and its folder, Backport needs the command-line tools its instructions call (git and gh).

Does Backport access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Backport safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Backport use?

Backport is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Backport use?

About 862 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Backport?

Skills that share tags, products or a category with Backport: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Backport?

GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/spring-cloud-gcp, which has 554 GitHub stars. The repository was last updated on October 6, 2026.

Source: GoogleCloudPlatform/spring-cloud-gcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.