How do I install the Update Reth skill?

Run npx skillmds@latest add ethereum-optimism/update-reth 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 Update Reth safe to use?

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

Which AI agents work with Update Reth?

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 Update Reth free to use?

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

Who published Update Reth?

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

Update Reth by ethereum-optimism — Agent Skill

Name: Update Reth
Author: ethereum-optimism

Update Reth

Update the pinned upstream reth dependency across the Rust workspaces — pin bump, shared dependency sync, compile-and-adapt loop, full verification, and PR. Use when asked to bump, update, or upgrade reth (e.g. "update to reth v2.4.0").

File contents

Update reth

Bump the paradigmxyz/reth pin (normally to the latest release tag) and adapt the OP Stack Rust workspaces to upstream API changes.

The complete procedure — pin audit, the four manifests, shared dependency sync, lockfiles, the compile-and-adapt loop, and verification — lives in rust/UPDATING-RETH.md. Read it in full first and follow it exactly; this skill only adds the agent workflow around it. Don't restate the guide to the user — execute it.

Arguments

Optional target: a release tag (v2.4.0), a commit sha, or an upstream PR number. Default: the latest upstream release tag (gh release list --repo paradigmxyz/reth).

Workflow

Orient. Read the guide. Find a local paradigmxyz/reth checkout (ask the user if you can't find one) and fetch its tags — you'll need it for tag resolution, API archaeology, and diffing replicated code.
Isolate. Work in a fresh git worktree (or jj workspace) based on latest develop — never on the main checkout's working copy. Run mise trust in the new directory.
Execute the guide's procedure, including the current-pin audit before moving off it. Iterate the compile loop to green rather than enumerating breakages up front; don't ask the user to confirm each adaptation.
Verify everything the guide lists before any push. On memory-constrained machines, wrap heavy builds in systemd-run --user --scope -p MemoryMax=<n>G with reduced -j (not ulimit -v, which SIGABRTs rustc).
Ship. One commit (rust: update reth to <version>) describing the pin move, each shared dependency sync, and every API adaptation. Run the AI review before pushing — code, security, and the reth-update-reviewer agent (docs/ai/reth-update-review.md), which catches upstream changes that should have forced an op- change but produced no diff in our tree. PR to develop with verification results spelled out.
Compound. If this bump taught you something the guide doesn't cover, fold it into rust/UPDATING-RETH.md in the same PR.

---name: update-rethdescription: Update the pinned upstream reth dependency across the Rust workspaces — pin bump, shared dependency sync, compile-and-adapt loop, full verification, and PR. Use when asked to bump, update, or upgrade reth (e.g. "update to reth v2.4.0").---# Update rethBump the `paradigmxyz/reth` pin (normally to the latest release tag) and adapt theOP Stack Rust workspaces to upstream API changes.The complete procedure — pin audit, the four manifests, shared dependency sync,lockfiles, the compile-and-adapt loop, and verification — lives in[`rust/UPDATING-RETH.md`](../../../rust/UPDATING-RETH.md). **Read it in full firstand follow it exactly**; this skill only adds the agent workflow around it. Don'trestate the guide to the user — execute it.## ArgumentsOptional target: a release tag (`v2.4.0`), a commit sha, or an upstream PR number.Default: the latest upstream release tag (`gh release list --repo paradigmxyz/reth`).## Workflow1. **Orient.** Read the guide. Find a local `paradigmxyz/reth` checkout (ask the user if you can't find one) and fetch its tags — you'll need it for tag resolution, API archaeology, and diffing replicated code.2. **Isolate.** Work in a fresh git worktree (or jj workspace) based on latest `develop` — never on the main checkout's working copy. Run `mise trust` in the new directory.3. **Execute the guide's procedure**, including the current-pin audit before moving off it. Iterate the compile loop to green rather than enumerating breakages up front; don't ask the user to confirm each adaptation.4. **Verify everything the guide lists** before any push. On memory-constrained machines, wrap heavy builds in `systemd-run --user --scope -p MemoryMax=<n>G` with reduced `-j` (not `ulimit -v`, which SIGABRTs rustc).5. **Ship.** One commit (`rust: update reth to <version>`) describing the pin move, each shared dependency sync, and every API adaptation. Run the AI review before pushing — code, security, **and the `reth-update-reviewer` agent** (`docs/ai/reth-update-review.md`), which catches upstream changes that should have forced an op- change but produced no diff in our tree. PR to `develop` with verification results spelled out.6. **Compound.** If this bump taught you something the guide doesn't cover, fold it into `rust/UPDATING-RETH.md` in the same PR.

Frequently asked questions