菜单
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").
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Investigate an OP Stack fault dispute game during (or after) an incident — answer the user's questions and diagnose: why a challenger is disagreeing, doing a lot of moves, or contradicting itself; whether a proposal is valid; which op-node is at fault; and (after the fact) who wins the bonds. Read-only.
Build dependencies and run acceptance tests locally in the Optimism monorepo. Handles contracts, cannon prestates, Rust binaries, and optional kona prestate.
| name | update-reth |
| description | 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"). |
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.
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).
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.
