Wagmi Feature Development
wevm/wagmi
Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.
“Document code in this repository.”
$ npx skills add leanEthereum/leanSpec --skill doc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install leanEthereum/leanSpec doc --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/leanEthereum/leanSpec.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/doc .claude/skills/doc && 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 "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .claude/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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/leanEthereum/leanSpec/tree/main/.claude/skills/docType 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 leanEthereum/leanSpec --skill doc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install leanEthereum/leanSpec doc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/doc .agents/skills/doc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .agents/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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 leanEthereum/leanSpec --skill doc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install leanEthereum/leanSpec doc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/doc .cursor/skills/doc && 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 "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .cursor/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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/leanEthereum/leanSpec.git --path .claude/skills/doc--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 leanEthereum/leanSpec --skill doc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install leanEthereum/leanSpec doc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/doc .gemini/skills/doc && 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 "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .gemini/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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 leanEthereum/leanSpec docInstalls 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 leanEthereum/leanSpec --skill doc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/doc .github/skills/doc && 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 "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .github/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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 leanEthereum/leanSpec --skill doc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install leanEthereum/leanSpec doc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/doc .opencode/skills/doc && 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 "doc" agent skill from https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/doc into .opencode/skills/doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc", 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.
docDoc is a skill in leanEthereum/leanSpec (143 stars). Its SKILL.md is about 1.9k tokens. Licence: MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0b7d33e. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Doc loads about 1.9k tokens when it runs. Until then it costs about 9 tokens; SKILL.md has 669 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.
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.
The full file from leanEthereum/leanSpec at commit 0b7d33e, republished under its MIT licence (© leanEthereum). 669 words, ~1,939 tokens.
.claude/skills/doc/SKILL.md (or your agent's skills folder).Write or refine documentation for leanSpec code.
The atomic style rules live in .claude/rules/documentation.md — defer to that file.
This skill defines what to document, how to scope the work, and shows a gold-standard exemplar.
Determine what to document from the argument passed to /doc:
git diff and git diff --cached to identify scope.
Do not touch unchanged code.When an argument is provided, document the target fully — not just uncommitted changes. The argument overrides the diff-only restriction.
When a header doc grows past one overview line, organize the detail under these section names:
Never title a section "Why ..." (for example "# Why the finalized slot is the cutoff"). That phrasing reads as AI filler. State the rationale as plain prose, the way an engineer would explain it to a colleague.
Test docstrings stay short. A one-line summary is usually enough. Education goes inline in structured blocks:
Invariant: <rule the test enforces>
Fixture state: <concrete numbers>
Mutation: <what we change and why>
<ASCII diagram of before/after>Never write essay-style prose blocks in test docstrings.
Tests under tests/consensus/ follow one fixed skeleton so any vector reads the same way.
The full standard lives in .claude/rules/documentation.md under "Consensus test-vector docstrings".
The module-level file header is exactly one line.
The body carries no inline comments — the docstring is the single source of truth.
The skeleton is a one-line summary, then Given, When, Then. One atomic fact per bullet, fixed notation for blocks, validators, votes, and the chain.
def test_justified_divergence_self_heals_in_next_block(
fork_choice_test: ForkChoiceTestFiller,
) -> None:
"""
A block adopts the votes that justify a slot from a fork it did not extend.
Given
-----
- 4 validators; a slot needs 3 votes (2/3) to be justified.
- the chain:
genesis
- common(1)
- block_2(2) -> block_3(3)
- fork_4(4)
- block_3 includes V0's vote for block_2.
- fork_4 includes V1, V2, V3's votes for common.
- fork_4 reaches 3 votes, so it justifies slot 1.
- block_3 has only 1 vote, so it justifies nothing.
- the views diverge: node = slot 1, head chain = slot 0.
When
----
- block_5 is built on block_3, carrying no votes of its own.
Then
----
- block_5 pulls the slot-1 votes from the pool and includes them.
- the head chain justifies slot 1, matching the node.
- finalized stays at slot 0.
"""Reference exemplar: tests/consensus/lstar/fork_choice/test_attestation_source_divergence.py.
These are the failure modes most likely to slip into leanSpec PRs:
.claude/rules/documentation.md rule 2.The target style for a well-documented Python function in this project. Note the tight one-sentence-per-line header, the plain-prose rationale, the phase-labeled body, and the ASCII layout diagram.
def encode_bitlist(bits: Sequence[Boolean]) -> bytes:
"""
Encode a variable-length bitlist to SSZ bytes.
# Overview
Data bits are packed little-endian within each byte.
A single 1 bit is placed immediately after the last data bit.
The trailing bit lets the decoder recover the original count.
SSZ encodes bitlists as raw bytes with no length prefix.
Without that trailing bit, [1, 0] and [1, 0, 0, 0, 0, 0, 0, 0] would share the byte 0x01.
A trailing 1 bit is the smallest sentinel that disambiguates them.
# Layout
bits = [1, 0, 1] -> byte 0: 0 0 0 0 [1] 1 0 1 (delimiter at bit 3)
bits = [1] * 8 -> byte 0: 1 1 1 1 1 1 1 1
byte 1: 0 0 0 0 0 0 0 [1] (delimiter spills)
Args:
bits: The variable-length bit data.
Returns:
SSZ-encoded bytes containing the data bits and the delimiter.
"""
# Phase 1: handle the empty case.
#
# No data bits means the encoding is just the delimiter.
num_bits = len(bits)
if num_bits == 0:
return b"\x01"
# Phase 2: pack data bits little-endian into a byte array.
#
# Bit i of the input lands in byte i // 8 at position i % 8.
byte_len = (num_bits + 7) // 8
byte_array = bytearray(byte_len)
for i, bit in enumerate(bits):
if bit:
byte_array[i // 8] |= 1 << (i % 8)
# Phase 3: place the delimiter immediately after the last data bit.
#
# When the bit count is a multiple of 8, the delimiter has no room
# in the existing array and spills into a fresh trailing byte.
if num_bits % 8 == 0:
return bytes(byte_array) + b"\x01"
byte_array[num_bits // 8] |= 1 << (num_bits % 8)
return bytes(byte_array)Match this density of structure, brevity of lines, and use of concrete numbers and diagrams.
Before finishing a documentation pass, verify:
© leanEthereum, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/doc of leanEthereum/leanSpec.
Open the folder on GitHubat commit 0b7d33e
Doc 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 |
|---|---|---|---|---|---|---|
| Doc this skillleanEthereum/leanSpec | 143 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Wagmi Feature Developmentwevm/wagmi | 6.8k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Release Roundethereumjs/ethereumjs-monorepo | 2.8k | — | ~2k | Automated safety check: Pass | None | |
| Update Est Fixturesethereumjs/ethereumjs-monorepo | 2.8k | — | ~3.3k | Automated safety check: Pass | None | |
| Starknet JSstarknet-io/starknet.js | 1.3k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Lean Reviewgeanlabs/gean | 177 | — | ~1.5k | Automated safety check: Pass | None |
wevm/wagmi
Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
ethereumjs/ethereumjs-monorepo
Updates EthereumJS execution-spec test fixtures from an ethereum/execution-specs release, then (after a human merge) points the monorepo submodule, updates VM npm scripts, reports a first test run…
starknet-io/starknet.js
A skill your agent uses when writing or debugging JavaScript/TypeScript that interacts with Starknet through the starknet.js SDK — building Call objects or calldata, encoding/decoding Cairo types…
geanlabs/gean
Review a branch or PR's diff against main and report opportunities to subtract — simplify, delete, and reduce the number of concepts a reader has to hold in their head.
boundless-xyz/boundless
How to use the Boundless CLI — the primary interface for the Boundless ZK proof marketplace.
leanEthereum/leanSpec
Read-only, multi-agent audit of the leanSpec codebase. An agent skill from leanEthereum/leanSpec.
leanEthereum/leanSpec
Run leanSpec fixtures against a client implementation. An agent skill from leanEthereum/leanSpec.
leanEthereum/leanSpec
Quick-reference checklist for code review conventions in leanSpec
leanEthereum/leanSpec
Show what changed in leanSpec between devnet versions or HEAD
leanEthereum/leanSpec
Common developer workflows, commands, and troubleshooting for leanSpec
leanEthereum/leanSpec
Generate consensus layer test fixtures
Works with
Categories
Run `npx skills add leanEthereum/leanSpec --skill doc -a claude-code`. Or copy the skill folder (.claude/skills/doc in leanEthereum/leanSpec) into .claude/skills/doc in your project. Claude Code loads it when a task matches its description.
Run `npx skills add leanEthereum/leanSpec --skill doc -a codex`. Or copy the skill folder (.claude/skills/doc in leanEthereum/leanSpec) into .agents/skills/doc in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add leanEthereum/leanSpec --skill doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc, .gemini/skills/doc, .github/skills/doc and .opencode/skills/doc in your project.
Going by SKILL.md and its folder, Doc needs the command-line tools its instructions call (git).
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.
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.
Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Doc: Wagmi Feature Development (wevm/wagmi, 6.8k stars), Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars), Update Est Fixtures (ethereumjs/ethereumjs-monorepo, 2.8k stars) and Starknet JS (starknet-io/starknet.js, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
leanEthereum (a GitHub organization) maintains it in leanEthereum/leanSpec, which has 143 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 2, 2026.
Source: leanEthereum/leanSpec on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.