// Use when about to create a PR or push changes in flutter_rust_bridge to ensure code generation is up to date
Use when the user wants Docker-based FRB development or Tart-based iOS Simulator validation.
Use when preparing or explaining the FRB Tart base VM for iOS Simulator validation, including local OCI registry mirroring, direct OCI clone, and base VM hygiene.
Explain how cargokit is sourced, copied, and analyzed inside flutter_rust_bridge. Use when working on `integration_template/**/cargokit`, `frb_example/**/cargokit`, integrate/generate output drift, or any diff that mentions cargokit and you need to identify the true source of truth before judging the change.
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, request and resolve Gemini review, and keep following up on a 5 minute cadence until the PR is ready.
Review a flutter_rust_bridge PR before treating it as ready, including subagent checks for correctness and test weakening plus Gemini review.
Use when needing to run tests locally in flutter_rust_bridge, or when debugging test failures before pushing
| name | frb-prepare-pr |
| description | 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, lint passes, and bug fixes have a concrete reproduction report in the PR description. Before treating a non-trivial PR as ready, run frb-pr-review.
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. For integrate output diffs, verify templates and run precommit-integrate
|
+-- 3. Read frb-lint skill --> Run lint --fix
|
+-- 4. (Optional) Read frb-test skill --> Run relevant tests
|
+-- 5. For non-trivial PRs, read frb-pr-review --> Run review gate
|
+-- 6. For bug fixes, add the reproduction report to the PR description
|
+-- 7. Commit all changes
|
+-- 8. Create PR (use creating-pull-requests skill)
frb-code-generation skill, run commands if neededfrb_codegen/assets/integration_template/ is the source that should change, then run ./frb_internal precommit-integratecargokit files under frb_example/**, read frb-cargokit, then run ./frb_internal sync-cargokit-copiesfrb-lint skill, run ./frb_internal lint --fixfrb-test skill, run relevant testsfrb-pr-review, run the review gate before final readinessfrb-develop-feature, including baseline commit, mechanical steps, observed failure, and expected behaviorCI 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.
If the PR changes integrate-generated example output but not frb_codegen/assets/integration_template/, explicitly verify that the output-only change is intentional. Most integrate scaffold behavior should be fixed in the template and regenerated, not patched only in frb_example/**.
frb-code-generation - Determines which generation commands to runfrb-lint - Lint and format checksfrb-test - For local debugging when CI failsfrb-pr-review - PR readiness review gatecreating-pull-requests - Standard PR creation process