Agent skill

Review

by leanEthereum in leanEthereum/leanSpec

Quick-reference checklist for code review conventions in leanSpec

MITAuto-check passedDevelopment

Install Review

skills CLI
$ npx skills add leanEthereum/leanSpec --skill review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install leanEthereum/leanSpec review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/leanEthereum/leanSpec.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review .claude/skills/review && rm -rf skills-src

Use ~/.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/

Facts

Skill name
review
GitHub stars
143
Token cost
~468 tokens
SKILL.md length
206 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Quick-reference checklist for code review conventions in leanSpec

  • Tasks that involve Code review
  • SKILL.md covers Imports, Type Annotations, Code Style and Documentation, plus 3 more sections
  • Calls just

What it does

Review is an agent skill from leanEthereum/leanSpec. Quick-reference checklist for code review conventions in leanSpec

Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. It works with Ethereum. The repository describes itself as: Lean Ethereum protocol specifications and test vector generation framework. The licence is MIT.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “/review”

What it can do on your machine

Read from SKILL.md and the folder at commit 0b7d33e. 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:

    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Review loads about 468 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 206 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~468

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

The full file from leanEthereum/leanSpec at commit 0b7d33e, republished under its MIT licence (© leanEthereum). 206 words, ~468 tokens.

Download SKILL.mdSave it as .claude/skills/review/SKILL.md (or your agent's skills folder).
name
review
description
Quick-reference checklist for code review conventions in leanSpec

/review - Code Review Checklist

A concise checklist distilled from CLAUDE.md for reviewing leanSpec code.

Imports

  • All imports at file top — no lazy imports inside functions
  • No confusing renames — use qualified access (x25519.X25519PublicKey)
  • from __future__ import annotations in every file

Type Annotations

  • Never quote annotations when from __future__ import annotations is present
  • Prefer narrow domain types (Bytes32, PeerId, RequestId) over raw bytes
  • Complete type hints on all function signatures

Code Style

  • Line length: 100 characters max
  • Google docstring style
  • No example code in docstrings — unit tests serve as examples
  • No section separator comments (# ====, # ----)
  • Module-level constants use docstrings, not comments

Documentation

  • Never use explicit function or method names in docs — names change
  • Write short, scannable sentences — one idea per line
  • Use bullet points or numbered lists for multiple items
  • Never remove existing documentation unless directly invalidated by a code change

Testing

  • Full equality assertions — assert the whole object, not individual fields
  • Descriptive test names explaining the scenario
  • Use pytest.raises(ExceptionType, match=r"...") for error tests
  • Boundary values derived from source constants, never hardcoded

Architecture

  • No backward compatibility code — no shims, aliases, or re-exports
  • No unnecessary abstractions — inline is often better for spec code
  • Simplicity over abstraction — readers should understand top-to-bottom
  • SSZ types: domain-specific names (Attestations) over generic (List4096)

Before Committing

bash
just fix    # Auto-fix lint, formatting, and markdown
just check  # Verify all checks pass

© leanEthereum, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/review of leanEthereum/leanSpec.

Open the folder on GitHubat commit 0b7d33e

Compare with similar skills

Review 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.

Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review this skillleanEthereum/leanSpec143—~468Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Backend Code Reviewlangflow-ai/langflow156k—~3.5kAutomated safety check: NotesMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Backend Code Review

    langflow-ai/langflow

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check: notes
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed

More from leanEthereum/leanSpec

All 9 skills in this repo
  • Audit

    leanEthereum/leanSpec

    Read-only, multi-agent audit of the leanSpec codebase. An agent skill from leanEthereum/leanSpec.

    143 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Client Test

    leanEthereum/leanSpec

    Run leanSpec fixtures against a client implementation. An agent skill from leanEthereum/leanSpec.

    143 GitHub stars~594 tokensUpdated 1 mo ago
    Auto-check passed
  • Spec Diff

    leanEthereum/leanSpec

    Show what changed in leanSpec between devnet versions or HEAD

    143 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Workflows

    leanEthereum/leanSpec

    Common developer workflows, commands, and troubleshooting for leanSpec

    143 GitHub stars~496 tokensUpdated 1 mo ago
    Auto-check passed
  • Doc

    leanEthereum/leanSpec

    Document code in this repository.

    143 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Fill

    leanEthereum/leanSpec

    Generate consensus layer test fixtures

    143 GitHub stars~202 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Review

What does Review do?

Quick-reference checklist for code review conventions in leanSpec. Review is an agent skill from leanEthereum/leanSpec.

When should I use Review?

Review fits situations like: tasks that involve Code review.

How do I install Review in Claude Code?

Run `npx skills add leanEthereum/leanSpec --skill review -a claude-code`. Or copy the skill folder (.claude/skills/review in leanEthereum/leanSpec) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.

How do I install Review in Codex?

Run `npx skills add leanEthereum/leanSpec --skill review -a codex`. Or copy the skill folder (.claude/skills/review in leanEthereum/leanSpec) into .agents/skills/review in your project. Codex loads it when a task matches its description.

Can I use Review 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 leanEthereum/leanSpec --skill review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.

What does Review need to run?

Going by SKILL.md and its folder, Review needs the command-line tools its instructions call (just).

Does Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Review 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 Review use?

Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review use?

About 468 tokens (SKILL.md is roughly 1.9k 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 Review?

Skills that share tags, products or a category with Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review?

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.