Frb Debugging
Testing & Qualityfrb-debuggingFrb Debugging is an Agent Skill for testing & quality published in the fzyzcjy/flutter_rust_bridge repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when generated code looks wrong, code generation fails, or you need to understand FRB internals
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/fzyzcjy/flutter_rust_bridge/blob/HEAD/.claude/skills/frb-debugging/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/frb-debugging, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
FRB Debugging
Note: Check your user-level
remote-testingrules before running commands. Codegen and debugging may require remote execution.
When to Use
- Generated code looks wrong
- Code generation fails
- Need to understand FRB internals
- Runtime errors in generated code
Quick Diagnostics
Dump Intermediate Representations
The in-tree examples by default enable dump_all: true in flutter_rust_bridge.yaml for debugability.
Therefore, you can check rust/target/frb_dump/ for:
- Effective configuration
- IR (intermediate representation)
- Generated spec and code
- ...
Debug Logs
RUST_LOG=debug flutter_rust_bridge_codegen ...
Full Troubleshooting
If above doesn't help, see:
website/docs/docs/guides/contributing/tip.mdwebsite/docs/manual/troubleshooting.md
Before going deep into FRB internals, first check whether you are actually seeing failure propagation from unstable generated outputs or integrate templates.
In particular:
- If CI failures may be explained by failure propagation, repeated package-level drift, or unstable generated outputs, you MUST use
frb-fix-cifirst - You MUST only stay in
frb-debuggingafterfrb-fix-cihas ruled out those simpler explanations
Related Skills
frb-code-generation- Which generation commands to runfrb-fix-ci- Diagnose CI failure propagation before deep debuggingfrb-develop-feature- Development workflow