Use when about to create a PR or push changes in flutter_rust_bridge to ensure code generation is up to date
Note: Check your user-level
remote-testingrules before running commands. Codegen, lint, and tests may require remote execution.
Before creating a PR, ensure generated code is up to date and lint passes.
Core principle: Generate → Lint → Commit → PR.
After codegen: Check your user-level
remote-testingrules. If codegen was run remotely, pull changes back to local.
1. Read frb-code-generation skill
|
+-- Run required generation commands
|
+-- 2. Read frb-lint skill --> Run lint --fix
|
+-- 3. (Optional) Read frb-test skill --> Run relevant tests
|
+-- 4. Commit all changes
|
+-- 5. Create PR (use creating-pull-requests skill)
frb-code-generation skill, run commands if neededfrb-lint skill, run ./frb_internal lint --fixfrb-test skill, run relevant testsCI automatically runs:
Run lint locally to avoid CI failures. Tests are optional locally.
If your PR fixes Flutter integrate example outputs and the real bug is inside the embedded cargokit submodule, do not stop at copied example files. Push the cargokit fix to fzyzcjy/cargokit and update the submodule ref in this repo before pushing the PR branch.
frb-code-generation - Determines which generation commands to runfrb-lint - Lint and format checksfrb-test - For local debugging when CI failscreating-pull-requests - Standard PR creation process