erigontech

Read and interpret the results, logs and artifacts of Erigon's QA workflows (the `qa-*.yml` GitHub Actions workflows - tip tracking, sync from scratch, exec from zero, snapshot download, clean exit, RPC integration/performance). Use when asked why a QA test…

Run repeatable benchmarkoor performance benchmarks against Erigon on current and future devnets, using protected native Linux OverlayFS with either pristine State Actor datadirs or pre-populated snapshots. Use for generic benchmark testing, compute or…

Compact an existing MDBX database instance to reclaim free/reclaimable space. Use this when the user wants to shrink mdbx.dat, reclaim MDBX garbage-collected pages, or fix MDBX_MAP_FULL issues.

Run Ethereum Hive integration tests against a local Erigon build, including engine, RPC compatibility, stable and devnet EEST EngineX, and RLP suites. Use when setting up an ephemeral Hive environment, selecting or running Hive suites, interpreting Hive…

Run the full Erigon test suite locally using GOGC=80 make test-all. Use this before marking a PR ready for review. Equivalent to the "All tests" CI workflow.

Run Erigon tests with Go race detector to find data races and concurrency bugs. Use this for concurrency-sensitive changes (parallel executor, p2p, txpool). Takes 30-60 minutes.

Run integrity checks on Erigon datadirs using the 'erigon seg integrity' command. Use this when the user wants to verify snapshot/segment file integrity or during the snapshot publishing process.

Run Erigon CI checks locally and/or trigger them remotely on a branch via GitHub Actions workflow_dispatch. Use this when you need to verify a branch passes all CI before or after pushing — especially for branches like bal-devnet-2 that don't auto-trigger on…

Use to add a performance pattern for rpc_perf, e.g. "I found a tx where the node is slow, where do I save it?", or to build a pattern from a block range or a profile, and to replay it with rpc_perf. Covers the tx lists of rpc_pattern_gen --txs, the per-tx…

Use to run RPC performance tests (rpc_perf) against a running node with an existing pattern, read the latencies and errors, and compare runs, e.g. a branch against main or one node against another. To build a new pattern use the perf-pattern-add skill.

Use to run the RPC integration tests (rpc_int) against a running node, the whole suite or some APIs or tests, and to read the failures. Use when the user wants to check a node or a branch against the expected JSON-RPC responses.

Use to run standalone Erigon RpcDaemon on an existing datadir. Use when the user wants to exercise the `rpc-tests` binaries (`rpc_int`, `rpc_perf`) against real server.

Use to run Erigon on an existing datadir. Use when the user wants to exercise the `rpc-tests` binaries (`rpc_int`, `rpc_perf`) against real server.

Use to execute Ethereum mainnet blocks from a local directory (dry run). Use it to execute downloaded blocks without proving.

Use to fetch Ethereum mainnet blocks from an RPC URL and save them on a local directory. Use it to acquire blocks for later execution/proving.

Use when the user asks to "benchmark", "run benchmark", "compare performance", "profile blocks", "cycle count comparison", or discusses SP1 prover performance testing. Runs batch block execution benchmarks and compares C++ vs Rust (or other) provers.

Analyze snapshot automation PR changes and produce a structured review report. Use when asked to summarize or review a snapshot PR.

Work in the vm-bench repo (cross-client EVM, node and RPC benchmarks, results page at erigontech.github.io/vm-bench). Use for any change to fixtures, runners, workloads, history snapshots or the page, and before measuring anything on the bench boxes.