技能 代码 风格 Contrib
- 作者仓库星标 1,008
- 作者仓库 trezor-suite
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.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @trezor · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。You have two options for contributing to the code style guide:
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…
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…
# 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](https://github.com/trezor/trezor-suite/issues?q=is%3Aissue%20state%3Aopen%20label%3Aproposal) before you [create a new one](https://github.com/trezor/trezor-suite/issues/new?template=08_code_improvement_proposal.md). 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.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> How to Contribute → 1. Create an Issue with a Proposal → 2. Create a Pull Request
要点 -> Everyone is welcome to make contributions! · Create a pull request with the proposed code style change so we can have a discussion directly in the PR.
文件/命令 -> github.com/trezor/trezor-suite/issues · github.com/trezor/trezor-suite/issues/new · 08codeimprovementproposal.md · and/or
内容 SHA-256 -> 10de4a1acd57
原文结构
适用与边界
原文中的明确线索
github.com/trezor/trezor-suite/issues、github.com/trezor/trezor-suite/issues/new、08codeimprovementproposal.md、and/or