skills-and-code-style-contribution
- Repo stars 1,008
- Author updated Live
- Author repo trezor-suite
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @trezor · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skills-and-code-style-contribution
description: How to contribute to the Trezor Suite code style guide, including issue proposals and pull reque…
category: engineering
runtime: no special runtime
---
# skills-and-code-style-contribution output preview
## PART A: Task fit
- Use case: How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes. You have two options for contributing to the code style guide: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “How to Contribute / 1. Create an Issue with a Proposal / 2. Create a Pull Request” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when proposing code style changes. You have two options for contributing to the code style guide: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “How to Contribute / 1. Create an Issue with a Proposal / 2. Create a Pull Request” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “How to Contribute / 1. Create an Issue with a Proposal / 2. Create a Pull Request”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skills-and-code-style-contribution
description: How to contribute to the Trezor Suite code style guide, including issue proposals and pull reque…
category: engineering
source: trezor/trezor-suite
---
# skills-and-code-style-contribution
## When to use
- How to contribute to the Trezor Suite code style guide, including issue proposals and pull request workflows. Use when…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “How to Contribute / 1. Create an Issue with a Proposal / 2. Create a Pull Request” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skills-and-code-style-contribution" {
input -> user goal + target files + boundaries + acceptance criteria
context -> How to Contribute / 1. Create an Issue with a Proposal / 2. Create a Pull Request
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review