FRB Prepare for PR
Note: Check your user-level
remote-testingrules before running commands. Codegen, lint, and tests may require remote execution.
Overview
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.
Workflow
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)
Quick Checklist
- REQUIRED: Read
frb-code-generationskill, run commands if needed - REQUIRED: Read
frb-lintskill, run./frb_internal lint --fix - (Optional) Read
frb-testskill, run relevant tests - Commit all changes
- Push and create PR
What CI Will Do
CI automatically runs:
- Code generation check (fails if generated code is outdated)
- All tests (Rust, Dart, Flutter, Web)
- Lint and format checks
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.
Related Skills
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
Converted and distributed by TomeVault — claim your Tome and manage your conversions.