菜单
Use when modifying Rust API, codegen, or example code in flutter_rust_bridge to determine which generation commands to run
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/fzyzcjy/flutter_rust_bridge --skill frb-code-generation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Review a flutter_rust_bridge PR before treating it as ready, including subagent checks for correctness and test weakening.
Update flutter_rust_bridge CHANGELOG.md for a new release by collecting merged PRs since the previous version tag, mapping them to the target release section, and formatting entries to match the existing changelog style. Use when writing or refreshing a release section in CHANGELOG.md.
Use when implementing a GitHub issue, bug fix, or feature in flutter_rust_bridge end-to-end: develop the change, add regression coverage, prepare and open a PR, monitor CI until green, and keep following up on a 5 minute cadence until the PR is ready.
基于 SOC 职业分类
正在显示 SKILL.md
| name | frb-code-generation |
| description | Use when modifying Rust API, codegen, or example code in flutter_rust_bridge to determine which generation commands to run |
Note: Check your user-level
remote-testingrules before running commands. Codegen may require remote execution.
flutter_rust_bridge requires code generation when Rust APIs change. This skill maps change types to the minimal generation commands needed.
Core principle: Run only the generation commands needed for your change type.
Validation rule: If regenerated outputs cause previously green non-Generate jobs to fail, treat the generated outputs as suspect until they are validated from a clean environment.
After codegen: Check your user-level
remote-testingrules. If codegen was run remotely, pull changes back to local.
| Change Type | Command |
|---|---|
Example Rust API (frb_example/**/rust/src/api/*.rs) | ./frb_internal precommit-generate |
| Flutter integrate examples | ./frb_internal precommit-integrate |
frb_codegen/ generation logic | ./frb_internal precommit-generate + generate-internal-rust |
frb_rust/src/ core API | ./frb_internal generate-internal-rust |
frb_example/pure_dart generator | ./frb_internal generate-internal-frb-example-pure-dart |
| CLI help documentation | ./frb_internal generate-internal-book-help |
Root README.md or CHANGELOG.md | ./frb_internal generate-internal-readme |
Other non-generated docs, comments, tests, or frb_dart/ source | No generation needed |
Treat the root README.md and CHANGELOG.md as sources of truth. After changing either file, run:
./frb_internal generate-internal-readme
Commit the generated package documentation in the same change. Do not manually edit frb_dart/README.md, frb_dart/CHANGELOG.md, or frb_hooks/CHANGELOG.md.
If a diff touches Flutter integrate example outputs, platform scaffolds, or copied cargokit files under frb_example/**, check whether the real source of truth should also change under frb_codegen/assets/integration_template/.
Do not submit only downstream integrate output changes when the behavior belongs in the template. Update the template first, then run:
./frb_internal precommit-integrate
Treat frb_codegen/assets/integration_template/**/cargokit as the source of truth for copied cargokit output. If the actual bug belongs inside the external cargokit submodule, read the frb-cargokit skill before deciding whether to patch the submodule and update its pointer.
For CI diagnosis rules about generated-file format/lint failures, repeated package-level Generate drift, or Generate :: FRB Codegen :: Command Integrate failures, you MUST read frb-fix-ci first. This skill is for command selection, not CI failure-propagation diagnosis.
For pure_dart / pure_dart_pde generation issues, treat frb_example/pure_dart as the upstream source and frb_example/pure_dart_pde as the derived copy. See frb-fix-ci for the CI diagnosis workflow.
If CI repair has already entered repeated package-level drift, you MUST stop choosing narrower commands and switch to frb-fix-ci.
Do not manually patch generated files as the final fix. The final accepted result should be produced by the corresponding generation command in a clean matching environment.