Dev Rules
rust-dd/tako
General coding-style rules to apply to every project. An agent skill from rust-dd/tako.
A skill your agent uses when updating this repo to match a new jito-solana release line such as v4.0.
Install Release Rebase
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebase --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-rebase .claude/skills/release-rebase && rm -rf skills-srcUse ~/.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/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .claude/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebase --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/release-rebase .agents/skills/release-rebase && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .agents/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebase --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/release-rebase .cursor/skills/release-rebase && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .cursor/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jito-foundation/geyser-grpc-plugin.git --path .codex/skills/release-rebase--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebase --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/release-rebase .gemini/skills/release-rebase && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .gemini/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/release-rebase .github/skills/release-rebase && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .github/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jito-foundation/geyser-grpc-plugin release-rebase --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jito-foundation/geyser-grpc-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/release-rebase .opencode/skills/release-rebase && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-rebase" agent skill from https://github.com/jito-foundation/geyser-grpc-plugin/tree/master/.codex/skills/release-rebase into .opencode/skills/release-rebase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-rebase", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-rebase- GitHub stars
- 145
- Token cost
- ~836 tokens
- SKILL.md length
- 428 words
- Files
- 2
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when updating this repo to match a new jito-solana release line such as v4.0.
- Works in 11 steps: Create a release branch named vX.X from… → Inspect the matching jito-solana vX.X… → Update Cargo.toml to the target release… → …
- Updating this repo to match a new jito-solana release line such as v4.0
- SKILL.md covers Workflow, Working Rules, Typical Failure Modes and Output Expectations
- Calls cargo and git
What it does
Release Rebase is an agent skill from jito-foundation/geyser-grpc-plugin. Use this skill when updating this repo to match a new jito-solana release line such as v4.0. It is for branch creation, toolchain and Cargo version alignment, mixed Solana dependency cleanup, API/struct migration work, validation, CI readiness, and final commit plus summary generation.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Backend & APIs, covering gRPC and Protobuf. It works with Solana, gRPC and Rust. The repository describes itself as: Solana Geyser plugin for account and slot updates over GRPC.
When your agent uses it
- Updating this repo to match a new jito-solana release line such as v4.0
- Tasks that involve gRPC and Protobuf
Example prompts
- “/release-rebase”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- Create a release branch named vX.X from the current branch, for example v4.0.
- Inspect the matching jito-solana vX.X branch and update rust-toolchain.toml to match its Rust channel and required components.
- Update Cargo.toml to the target release line, including agave-geyser-plugin-interface = "=X.Y.Z" and any related Solana/Agave crate…
- Run cargo check --workspace early. Fix version skew first
- Fix compile errors caused by API or struct changes
- Re-run cargo check --workspace until it passes.
- Run cargo clippy --all-features -- -D clippy::all.
- Run cargo test --workspace.
- If the repo has CI or additional validation commands, run the same checks locally before finishing.
- Commit only when validation passes. Use git commit --no-gpg-sign.
- Produce a short summary covering
What it can do on your machine
Read from SKILL.md and the folder at commit c9a9961. 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:
cargogit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Release Rebase loads about 836 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 428 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 428 words (~836 tokens).
“Rebase this plugin to a target jito-solana release branch with a compile-first workflow. Use it when the repo needs to move from one Solana/Agave release line to another and the likely work includes dependency graph cleanup and source updates.”
- name
- release-rebase
Files
SKILL.md and 1 other file in .codex/skills/release-rebase of jito-foundation/geyser-grpc-plugin.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit c9a9961
Compare with similar skills
Release Rebase 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Rebase this skilljito-foundation/geyser-grpc-plugin | 145 | — | ~836 | Automated safety check: Pass | Custom licence | |
| Dev Rulesrust-dd/tako | 162 | — | ~810 | Automated safety check: Pass | MIT | |
| SpikardGoldziher/spikard | 123 | — | ~799 | Automated safety check: Pass | MIT | |
| Docs Writingrust-dd/tako | 162 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Release WorkflowGoldziher/spikard | 123 | — | ~909 | Automated safety check: Pass | MIT | |
| Nemo Relay Plugin BuildNVIDIA/NeMo-Relay | 192 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Spikard
Goldziher/spikard
Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.
Docs Writing
rust-dd/tako
Conventions for writing and maintaining tako documentation pages under website/content/docs/.
Release Workflow
Goldziher/spikard
Release/publish the spikard Rust core crate and CLI end-to-end.
- Official
Nemo Relay Plugin Build
NVIDIA/NeMo-Relay
A skill your agent uses when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed rustdynamic native or worker gRPC plugin, with…
Quicknode Skill
internet-court/internet-court-skill
Quicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap…
Related
Categories
Questions about Release Rebase
What does Release Rebase do?
A skill your agent uses when updating this repo to match a new jito-solana release line such as v4.0. Release Rebase is an agent skill from jito-foundation/geyser-grpc-plugin.0.
When should I use Release Rebase?
Release Rebase fits situations like: updating this repo to match a new jito-solana release line such as v4.0; tasks that involve gRPC and Protobuf.
How do I install Release Rebase in Claude Code?
Run `npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a claude-code`. Or copy the skill folder (.codex/skills/release-rebase in jito-foundation/geyser-grpc-plugin) into .claude/skills/release-rebase in your project. Claude Code loads it when a task matches its description.
How do I install Release Rebase in Codex?
Run `npx skills add jito-foundation/geyser-grpc-plugin --skill release-rebase -a codex`. Or copy the skill folder (.codex/skills/release-rebase in jito-foundation/geyser-grpc-plugin) into .agents/skills/release-rebase in your project. Codex loads it when a task matches its description.
Can I use Release Rebase 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 jito-foundation/geyser-grpc-plugin --skill release-rebase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-rebase, .gemini/skills/release-rebase, .github/skills/release-rebase and .opencode/skills/release-rebase in your project.
What does Release Rebase need to run?
Going by SKILL.md and its folder, Release Rebase needs the command-line tools its instructions call (cargo and git).
Does Release Rebase access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Rebase 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 Release Rebase use?
Release Rebase has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Release Rebase use?
About 836 tokens (SKILL.md is roughly 3.3k 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 Release Rebase?
Skills that share tags, products or a category with Release Rebase: Dev Rules (rust-dd/tako, 162 stars), Spikard (Goldziher/spikard, 123 stars), Docs Writing (rust-dd/tako, 162 stars) and Release Workflow (Goldziher/spikard, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Rebase?
jito-foundation (a GitHub organization) maintains it in jito-foundation/geyser-grpc-plugin, which has 145 GitHub stars. The repository was last updated on August 27, 2026.
Source: jito-foundation/geyser-grpc-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.