@trezor/skills-and-code-style-contribution
BHow to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.
Install
agr install @trezor/skills-and-code-style-contribution --target claudeWrites 1 file into .claude/skills/, pinned to git-89e2cc77.
- .claude/skills/skills-and-code-style-contribution/SKILL.md
Document
name: skills-and-code-style-contribution description: How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.
Skills and Code Style Contribution
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.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-89e2cc778b5c2026-07-31