Skills and Code Style Contribution
SkillDev toolsHow to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skills and Code Style Contribution skill
What this skill tells your AI
The instructions your AI receives, as published by trezor/trezor-suite in skills/skills-and-code-style-contribution/SKILL.md and read by ahel’s review.
How to Contribute
You have two options for contributing to the code style guide:
1. Create an Issue with a Proposal
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.
2. Create a Pull Request
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.
Signals
- GitHub stars
- 1k
- Forks
- 375
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
skills-and-code-style-contribution- Source
- github.com/trezor/trezor-suite