agentleFS
Sign inStart free
leanEthereumleanEthereum/leanSpec/.claude/skills/client-test/SKILL.md

client-test

Skill143 starsChanged 2 months agoMITView on GitHub

Run leanSpec fixtures against a client implementation

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run generated leanSpec test fixtures against a client implementation.

    line 8
  2. Very specific:

    Remove old fixtures at the destination, then copy the contents of fixtures/consensus/ to the destination (destination path is …

    line 32
  3. Distinctive:

    Run the test command from the client's test workdir (path is client-dependent).

    line 36
  4. Distinctive:

    If zero tests ran, warn that the client may need to update its test runner to scan the new devnet fixture path.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/client-test - Client Integration Testing

Run generated leanSpec test fixtures against a client implementation.

Usage

/client-test <client-name> e.g. /client-test ream

Steps

1. Check fixtures exist

Generated fixtures live at fixtures/consensus/. Verify it contains JSON files. If empty or missing, generate them:

uv run fill --fork=Lstar --clean -n auto --scheme=prod

Fixtures for client testing must always use --scheme=prod (production signatures).

2. Clone or update client

Clone the client repo into clients/ (gitignored). If already cloned, pull latest.

3. Sync fixtures

Remove old fixtures at the destination, then copy the contents of fixtures/consensus/ to the destination (destination path is client-dependent).

4. Run tests

Run the test command from the client's test workdir (path is client-dependent). Show full output. Do not abort early on test failures.

If zero tests ran, warn that the client may need to update its test runner to scan the new devnet fixture path.

Clients

ream

  • Repo: https://github.com/ReamLabs/ream.git
  • Fixture destination (relative to repo root): testing/lean-spec-tests/fixtures/lstar
  • Test workdir (relative to repo root): testing/lean-spec-tests
  • Test command: cargo test --release --features lean-spec-tests

zeam

  • Repo: https://github.com/blockblaz/zeam.git
  • Fixture destination (relative to repo root): leanSpec/fixtures/consensus (leanSpec is a git submodule)
  • Test workdir (relative to repo root): . (repo root)
  • Test commands (run in order):
    1. zig build spectest:generate --summary all (generate Zig test wrappers from JSON fixtures)
    2. zig build spectest:run --summary all (run the spec tests)

qlean-mini

  • Repo: https://github.com/qdrvm/qlean-mini.git
  • Branch: spec/test-vectors (test vector infrastructure is not on master)
  • Fixture destination (relative to repo root): tests/test_vectors/fixtures/consensus
  • Test workdir (relative to repo root): . (repo root)
  • Test commands (run in order):
    1. cmake --preset default (configure)
    2. cmake --build build -j (build)
    3. ctest --test-dir build -R test_vectors_test --output-on-failure (run spec tests)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free