OpenParable
Skip to content
← Back to skills

Skills And Code Style Contribution

Development
skills-and-code-style-contribution

Skills And Code Style Contribution is an Agent Skill for development published in the trezor/trezor-suite repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/trezor/trezor-suite/blob/HEAD/skills/skills-and-code-style-contribution/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/skills-and-code-style-contribution, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.