A Git workflow command for rebasing an OpenShift fork onto a specified upstream release. Rebasing reapplies the fork's changes on top of newer changes from the original repository.

Use it to update the repository to a chosen release or find the latest stable upstream release, while checking the required remotes and commit format.

It organizes the repeated fetch, branch, tag, and commit steps needed to keep an OpenShift fork aligned with upstream.

rebase — Command for Claude Code by wangke19/gemini-ai-helpers

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/rebase/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/rebase)

Your own site

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/rebase"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/rebase/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/rebase"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/rebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,734 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.01734
Opus 5.5	$0.00006	$0.00694
Sonnet 5.5	$0.00003	$0.00347
Haiku 4.5	$0.00002	$0.00173

Measured 1mo ago against content hash 31f0983f9531, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rebase scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

extensions/openshift/commands/rebase.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

openshift:rebase

Synopsis

/openshift:rebase [tag]

Description

The /openshift:rebase command rebases git repository in the current working directory to a new upstream release specified by [tag]. If no [tag] is specified, the command tries to find the latest stable upstream release.

The repository must follow rules described in https://github.com/openshift/kubernetes/blob/master/REBASE.openshift.md, namely all OpenShift-specific commits must have prefix UPSTREAM:.

Implementation

Pre-requisites

Three local remote repositories should be tracked from a local machine: origin tracking the user's fork of this repository, openshift tracking this repository and upstream tracking the upstream repository.

To verify the correct setup, use

git remote -v

Fail, if there is no upstream, origin or openshift remote.

Rebase to the new upstream version

Fetch all the remote repositories including tags
```
git fetch --all
```
Find the main branch of the repository. It's either master or main. In the following steps, we will use master, but replace it with the main branch.
If user did not specify an upstream tag to rebase to as <tag>, find the greatest upstream tag that is not alpha, beta or rc.
Create a new branch based on the newest tag $1 of the upstream repository. Name it after the tag.
```
git checkout -b rebase-<tag> <tag>
```
Merge openshift/master branch into the rebase-$1 branch with merge strategy ours:
```
git merge -s ours openshift/master
```
Find the last rebase that has been done to openshift/master. We will use the upstream tag used for this rebase as $previous_tag.
Find the merge base of the openshift/master and $previous_tag by running git merge-base openshift/master $previous_tag. We will use this merge base as $mergebase.
Prepare commits.tsv tab-separated values file containing the set of carry commits in the openshift/master branch that need to be considered for picking:

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 147 lines · 15 tokens per session scan A 31f0983f9531

Subscribe to this mod's changes

rebase is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,734 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Git and workflow Releases extentions gemini-cli openshift redhat

wtfp:update

Check for a newer compatible package or plugin release and install it only after approval.

akougkas/wtf-p · 20 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

rebase