Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.
.claude/skills/trezor-skills-and-code-style-contribution/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -53% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -60% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -70% | 0% |
You have two options for contributing to the code style guide:
Everyone is welcome to make contributions! Check the list of current proposals before you create a new one. These proposals shall later be discussed at the Code Improvements meetings with members of the Suite team. Once we agree on a preferred solution, the person who added the proposal is responsible for implementing any related changes to the codebase and/or documenting the decision in this guide.
Create a pull request with the proposed code style change so we can have a discussion directly in the PR. This is a good option for smaller changes that don't require much discussion and are not that controversial. For larger changes, we recommend creating an issue first to have a more focused discussion before implementation.
Other measured skills in the registry, with their headline benchmark lift.