Standardizes the workflow for contributing code style changes to the Trezor Suite project.
Install
mkdir -p .claude/skills/skills-and-code-style-contribution && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16123" && unzip -o skill.zip -d .claude/skills/skills-and-code-style-contribution && rm skill.zipInstalls to .claude/skills/skills-and-code-style-contribution
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes.Key capabilities
- →Propose code style changes via GitHub issues
- →Create pull requests for code style changes
- →Discuss code style proposals with the Suite team
- →Implement agreed-upon style changes
- →Document code style decisions
How it works
The skill outlines two methods for contributing to the code style guide: creating an issue for discussion or creating a pull request for smaller changes.
Inputs & outputs
When to use skills-and-code-style-contribution
- →Propose new coding standards
- →Submit style guide PR
- →Discuss code improvement proposals
About this skill
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.
When not to use it
- →When the contribution is not related to code style
- →When the change is not intended for the Trezor Suite codebase
- →When the user wants to implement a large, controversial change without prior discussion
Limitations
- →Contributions are specific to the Trezor Suite code style guide.
- →Larger changes are recommended to start as an issue for discussion.
- →The process involves GitHub issues and pull requests.
How it compares
This skill provides a specific workflow for contributing to a code style guide, including issue templates and PR guidelines, unlike general code contributions.
Compared to similar skills
skills-and-code-style-contribution side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| skills-and-code-style-contribution (this skill) | 0 | 4mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| git-commits | 21 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by trezor
View all by trezor →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.