fill

Generate consensus layer JSON test fixtures from tests/consensus using tox-based fill.

143|80|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/leanEthereum/leanSpec --skill fill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fill
Source: https://github.com/leanEthereum/leanSpec/tree/main/.claude/skills/fill
Command: npx skills add https://github.com/leanEthereum/leanSpec --skill fill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consensus layer test fixtures is tedious and error-prone; this skill automates the process by running a dedicated test filler to produce consistent fixtures.

Core Features & Use Cases

  • Automates fixture generation from the consensus tests located in tests/consensus.
  • Supports generating fixtures for the Devnet by default and allows targeting specific forks (e.g., Electra) or specific test files.
  • Outputs the resulting JSON fixtures to fixtures/consensus for reuse in validation and testing workflows.

Quick Start

Run the fill skill to generate fixtures for the Devnet by default.

Frequently Asked Questions about fill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate consensus layer test fixtures?

To generate consensus layer test fixtures, you run a tox-based filler that discovers tests in tests/consensus and outputs JSON fixtures to fixtures/consensus. This automation replaces tedious manual generation by producing consistent test files for validation workflows. Default execution targets the Devnet environment.

Can I generate consensus test fixtures for a specific fork like Electra?

Yes, you can generate consensus test fixtures for specific forks like Electra. The fixture generation process supports targeting specific forks or specific test files instead of just using the default Devnet configuration, allowing you to create precise JSON test fixtures required for your specific development and testing workflows.

What is the tox-based fill process for consensus test discovery?

The tox-based fill process is an automated mechanism that discovers tests located in tests/consensus and generates corresponding JSON fixtures. It streamlines the development and testing workflow by automatically parsing test definitions and outputting reusable consensus layer test fixtures into the fixtures/consensus directory.

Do I need any specific dependencies to run consensus fixture generation?

No external dependencies are required to run the consensus fixture generation. The skill operates independently to discover tests and apply the tox-based fill mechanism, outputting the resulting JSON fixtures directly to fixtures/consensus for immediate reuse in your Devnet or specific fork validation workflows.

Where are the generated JSON consensus test fixtures outputted?

The generated JSON consensus test fixtures are outputted to the fixtures/consensus directory. By running the filler against the tests in tests/consensus, the process produces these reusable JSON fixture files to support validation and testing workflows for Devnet or targeted forks.

Why does manual consensus test fixture generation fail in testing workflows?

Manual consensus test fixture generation fails because it is tedious and error-prone, leading to inconsistent validation results. Automating the process with a dedicated test filler ensures consistent JSON fixtures are produced from tests/consensus, eliminating human error and streamlining Devnet and fork-specific testing workflows.