framework: add client-test skill#462
Merged
tcoratger merged 1 commit intoleanEthereum:mainfrom Mar 20, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🗒️ Description
It's been tedious to update the test vectors, regenerate them, then test them with clients. This PR teaches Claude how perform this flow. Generally I can now just ask "run tests on ream" and it does it consistently.
Without this skill Claude could still do it, but it will spend a lot of time and tokens to figure out how to run the test vectors on a client.
Technically it's also possible to write this as a script but I find this much simpler to maintain given a script will need to accommodate different client's behavior + manage the files. Also this way there's less non-specs code in the repo.