Saucebox Registry
← Browse

@fzyzcjy/frb-debugging

A

Use when generated code looks wrong, code generation fails, or you need to understand FRB internals

skillclaude

Install

agr install @fzyzcjy/frb-debugging --target claude

Writes 1 file into .claude/skills/, pinned to git-bde0db35.

  • .claude/skills/frb-debugging/SKILL.md

Document

name: frb-debugging description: Use when generated code looks wrong, code generation fails, or you need to understand FRB internals

FRB Debugging

Note: Check your user-level remote-testing rules 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.md
  • website/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-ci first
  • You MUST only stay in frb-debugging after frb-fix-ci has ruled out those simpler explanations

Related Skills

  • frb-code-generation - Which generation commands to run
  • frb-fix-ci - Diagnose CI failure propagation before deep debugging
  • frb-develop-feature - Development workflow

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-bde0db35ac4f2026-07-31