skills.rest
capitalexchange
capitalexchangeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fix-nethtest

Diagnose and fix failing Nethermind tests by analyzing traces and root causes.

Updated May 13, 2026
Search Tags:#debugging#ethereum#root-cause#tests#evm#trace-analysis#nethermind
One-click install
npx skills add https://github.com/capitalexchange/bourse --skill fix-nethtest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-nethtest
Source: https://github.com/capitalexchange/bourse/tree/main/.agents/skills/fix-nethtest
Command: npx skills add https://github.com/capitalexchange/bourse --skill fix-nethtest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix failing tests run with Nethermind.Test.Runner (nethtest) by analyzing traces and identifying root causes in the EVM/spec/test harness.

Core Features & Use Cases

  • Classify failures by running Phase 1 analysis on test traces.
  • Propose targeted fixes for opcode guards, gas accounting, and state-root discrepancies based on trace results.
  • Re-run tests and verify fixes, providing a clear remediation report.

Quick Start

Provide one or more test file paths to run Nethermind tests and automatically diagnose traces, identify root causes, and propose fixes.

Frequently Asked Questions about fix-nethtest

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

FAQPage Schema
How do I diagnose failing Ethereum Foundation tests in Nethermind.Test.Runner?▼

To diagnose failing Nethermind tests, you run an automated four-phase analysis on test traces to classify failures and identify root causes in the EVM, spec, or test harness. This process accepts one or more JSON test file paths as input to automatically execute tests and analyze the resulting trace outputs.

What is the best way to find the root cause of state-root discrepancies in EVM tests?▼

Finding the root cause of state-root discrepancies in EVM tests involves analyzing test execution traces to pinpoint failures in opcode guards or gas accounting. The diagnostic workflow classifies the failure and proposes targeted fixes based on the trace results and test JSON data.

Can I automatically verify fixes for Nethermind blockchain tests after applying changes?▼

Yes, you can automatically verify fixes for Nethermind blockchain tests by re-running the test execution phase. The workflow performs fix verification after proposing targeted remedies for opcode guards, gas accounting, or state-root discrepancies, providing a clear remediation report.

Does Nethermind test debugging work with Ethereum Foundation state and blockchain test formats?▼

Nethermind test debugging applies specifically to Ethereum Foundation state and blockchain tests run with Nethermind.Test.Runner. It accepts test file paths as input and relies on trace outputs, test JSON, and header defaults to guide the remediation workflow.

Why does my nethtest execution fail with opcode guard or gas accounting errors?▼

Your nethtest execution may fail due to incorrect opcode guards, gas accounting, or state-root discrepancies identified during the EVM trace analysis. The diagnostic workflow classifies these specific failure types from the test traces and proposes targeted fixes to resolve them.

Related Skills

Explore More Software Engineering Skills→
Unique-DivineUnique-Divine
6

evm-rpc

Retrieve EVM transaction receipts and run debug tracers via JSON-RPC.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
cyoteecyotee

tevm-debugging

Trace EVM transactions with execution steps and gas profiling.

Community
Advanced
gaebalaigaebalai
2

ci-flaky-triage

Analyze CI test logs to detect and classify flaky tests.

Community
Advanced