New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Frb Fix Main CI

by fzyzcjy in fzyzcjy/flutter_rust_bridge

A skill your agent uses when flutterrustbridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green…

MITAuto-check passedMobile

Install Frb Fix Main CI

skills CLI
$ npx skills add fzyzcjy/flutter_rust_bridge --skill frb-fix-main-ci -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fzyzcjy/flutter_rust_bridge frb-fix-main-ci --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fzyzcjy/flutter_rust_bridge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/frb-fix-main-ci .claude/skills/frb-fix-main-ci && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
frb-fix-main-ci
GitHub stars
5.4k
Token cost
~968 tokens
SKILL.md length
538 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when flutterrustbridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green…

  • Works in 5 steps: What is the failing default-branch… → What is the nearest older default-branch… → Which commits or merged PRs sit between… → …
  • Flutterrustbridge CI fails on the default branch/main/master
  • SKILL.md covers Choose a Path, Regression Workflow, What Not To Do and PR Expectations
  • Calls git

What it does

Frb Fix Main CI is an agent skill from fzyzcjy/flutter_rust_bridge. Use when flutterrustbridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit.

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Cross-platform mobile apps. It works with Flutter and Rust. The repository describes itself as: Flutter/Dart <- Rust binding generator, feature-rich, but seamless and simple. The licence is MIT.

When your agent uses it

  • Flutterrustbridge CI fails on the default branch/main/master
  • Especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit

Example prompts

  • “/frb-fix-main-ci”

Requirements

  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. What is the failing default-branch commit and workflow run?
  2. What is the nearest older default-branch commit with a green run for the same workflow or job family?
  3. Which commits or merged PRs sit between the green baseline and the red commit?
  4. Does the failure reproduce at the red commit but not at the green baseline, using the same ./frb_internal ... command and the FRB dev…
  5. Which source change most directly explains the regression?

What it can do on your machine

Read from SKILL.md and the folder at commit 848e438. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frb Fix Main CI loads about 968 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 538 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~968

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fzyzcjy/flutter_rust_bridge at commit 848e438, republished under its MIT licence (© fzyzcjy). 538 words, ~968 tokens.

Download SKILL.mdSave it as .claude/skills/frb-fix-main-ci/SKILL.md (or your agent's skills folder).
name
frb-fix-main-ci
description
Use when flutter_rust_bridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit.

FRB Fix Main CI

Use this when CI is failing on the default branch (main / master) or on a commit that is already part of the default-branch history.

Choose a Path

Default-branch CI failures usually have two possible repair paths. Choose based on the evidence in the latest relevant run.

Path A: Ordinary CI Repair

Use this path when the failure looks like a known FRB CI shape: flaky job, generated diff, lint drift, stale generated output, dependency-order failure, or downstream symptom already covered by existing CI triage.

Read frb-fix-ci and repair the failure directly:

  • Check the latest relevant run, not stale status.
  • Use the user's tom-ci skill when reading GitHub Actions job logs.
  • Classify flakes, generated diffs, lint drift, dependency-order failures, and propagated downstream symptoms before deep debugging.
  • Prefer fixing prerequisite jobs such as Generate, Integrate, or high-relevance Generate Internal before chasing later build/test symptoms.
Path B: Regression Investigation

Use this path when the failure is not obviously a known FRB CI maintenance issue, or when several default-branch commits/runs suggest something recently broke.

A default-branch failure is often a regression. There should usually be an older default-branch commit that passed the same CI path. Study what changed between the green baseline and the red commit, then fix the source of that regression.

Before writing a regression fix, answer these questions:

  1. What is the failing default-branch commit and workflow run?
  2. What is the nearest older default-branch commit with a green run for the same workflow or job family?
  3. Which commits or merged PRs sit between the green baseline and the red commit?
  4. Does the failure reproduce at the red commit but not at the green baseline, using the same ./frb_internal ... command and the FRB dev environment rules?
  5. Which source change most directly explains the regression?
Show full SKILL.md (248 more words)Show less

Regression Workflow

  1. Capture the exact failing jobs and the first useful error from CI logs.
  2. Find the newest passing default-branch run for the same workflow/job family.
  3. Compare the commit range between green and red:
    bash
    git log --oneline --decorate <green-sha>..<red-sha>
git diff --stat <green-sha>..<red-sha>
  4. If the range is broad or the culprit is unclear, bisect with the smallest meaningful reproduction command.
  5. Fix the source of the regression, not just the generated or downstream symptom.
  6. Add or adjust regression coverage when the bug is behavioral. For pure CI/tooling drift, document the before/after evidence in the PR.

What Not To Do

  • Do not treat default-branch CI as "just rerun until green" unless logs strongly indicate infra flake.
  • Do not force every default-branch failure through regression bisect when frb-fix-ci already identifies a direct CI maintenance fix.
  • Do not only repair checked-in generated files if the generator, template, version pin, or environment change is the real source.
  • Do not chase downstream job failures while an upstream generation or integration job is still red.
  • Do not assume the newest red commit is the sole cause without checking the nearest green baseline and intervening changes.

PR Expectations

For a PR that fixes default-branch CI, include:

  • Failing commit SHA and workflow/job URL.
  • Nearest green baseline SHA or run, if available.
  • The reproduction command used locally or in Docker/Tart.
  • The suspected or confirmed culprit commit/PR.
  • Why the fix addresses the source of the regression.

Use frb-prepare-pr before opening the PR.

© fzyzcjy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/frb-fix-main-ci of fzyzcjy/flutter_rust_bridge.

Open the folder on GitHubat commit 848e438

Compare with similar skills

Frb Fix Main CI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Frb Fix Main CI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frb Fix Main CI this skillfzyzcjy/flutter_rust_bridge5.4k—~968Automated safety check: PassMIT
Puremusicqingyueyin/Pure-music188—~907Automated safety check: PassGPL-3.0
Core API Changelibnativeapi/nativeapi166—~2.5kAutomated safety check: PassMIT
Winapp CLIboshi-xixixi/TraeSkill276—~1.9kAutomated safety check: PassMIT
Spec To Repoalirezarezvani/claude-skills28k—~2.7kAutomated safety check: NotesMIT
Engine Whats Newflutter/flutter180k—~978Automated safety check: PassBSD-3-Clause

Similar skills

  • Puremusic

    qingyueyin/Pure-music

    Pure-music 项目开发指南，覆盖 Windows Flutter/Dart 前端、Rust 后端、音频播放、歌词解析与渲染、桌面歌词、主题背景、设置、FFI、文档和测试。处理此仓库的代码理解、问题诊断、功能开发、缺陷修复、性能优化或代码审查时使用。

    188 GitHub stars~907 tokensUpdated today
    MobileAuto-check passed

  • Core API Change

    libnativeapi/nativeapi

    Carry a change to the C++ public API in core/ all the way downstream — design check, header edit, six platform implementations, C ABI + Rust/Dart/C/JS/Python regeneration, per-binding verification…

    166 GitHub stars~2.5k tokensUpdated today
    MobileAuto-check passed

  • Winapp CLI

    boshi-xixixi/TraeSkill

    Windows App Development CLI (winapp) for building, packaging, signing, debugging, and UI-automating Windows applications.

    276 GitHub stars~1.9k tokensUpdated 5 mo ago
    MobileAuto-check passed

  • Spec To Repo

    alirezarezvani/claude-skills

    A skill your agent uses when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'I…

    28k GitHub stars~2.7k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes

  • Engine Whats New

    flutter/flutter

    Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).

    180k GitHub stars~978 tokensUpdated today
    MobileAuto-check passed

  • Flutter Cherry Pick

    flutter/flutter

    How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel.

    180k GitHub stars~1.8k tokensUpdated today
    MobileAuto-check passed

More from fzyzcjy/flutter_rust_bridge

All 28 skills in this repo

  • Frb Add Contributor

    fzyzcjy/flutter_rust_bridge

    Add or reconcile flutterrustbridge contributors through all-contributors PRs.

    5.4k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Frb Android Emulator Prepare

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when preparing, installing, diagnosing, or explaining the host Android Emulator environment for flutterrustbridge local runtime validation, including Android SDK command-line…

    5.4k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check: notes

  • Frb Cargokit Dev

    fzyzcjy/flutter_rust_bridge

    Develop or update CargoKit for flutterrustbridge. An agent skill from fzyzcjy/flutter_rust_bridge.

    5.4k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Frb Categorize Code Diff

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when classifying a flutterrustbridge branch or PR diff into test and non-test changes, including colocated Rust test modules.

    5.4k GitHub stars~524 tokensUpdated yesterday
    Auto-check passed

  • Frb CI Filter

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when running focused flutterrustbridge GitHub Actions CI via cifilter, adding/removing the ci-manual-dispatch PR label, choosing exact CI jobs or matrix entries, documenting…

    5.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Frb Code Generation

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when modifying Rust APIs, codegen, generated examples, or platform scaffolds in flutterrustbridge to select generation commands and preserve source-of-truth and convergence…

    5.4k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Frb Fix Main CI

What does Frb Fix Main CI do?

A skill your agent uses when flutterrustbridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green…. Frb Fix Main CI is an agent skill from fzyzcjy/flutter_rust_bridge. Use when flutterrustbridge CI fails on the default branch/main/master, especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit.

When should I use Frb Fix Main CI?

Frb Fix Main CI fits situations like: flutterrustbridge CI fails on the default branch/main/master; especially to distinguish ordinary CI repair from a regression introduced after a previously green default-branch commit.

How do I install Frb Fix Main CI in Claude Code?

Run `npx skills add fzyzcjy/flutter_rust_bridge --skill frb-fix-main-ci -a claude-code`. Or copy the skill folder (.claude/skills/frb-fix-main-ci in fzyzcjy/flutter_rust_bridge) into .claude/skills/frb-fix-main-ci in your project. Claude Code loads it when a task matches its description.

How do I install Frb Fix Main CI in Codex?

Run `npx skills add fzyzcjy/flutter_rust_bridge --skill frb-fix-main-ci -a codex`. Or copy the skill folder (.claude/skills/frb-fix-main-ci in fzyzcjy/flutter_rust_bridge) into .agents/skills/frb-fix-main-ci in your project. Codex loads it when a task matches its description.

Can I use Frb Fix Main CI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fzyzcjy/flutter_rust_bridge --skill frb-fix-main-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frb-fix-main-ci, .gemini/skills/frb-fix-main-ci, .github/skills/frb-fix-main-ci and .opencode/skills/frb-fix-main-ci in your project.

What does Frb Fix Main CI need to run?

Going by SKILL.md and its folder, Frb Fix Main CI needs the command-line tools its instructions call (git). Our summary lists: Docker.

Does Frb Fix Main CI access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Frb Fix Main CI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Frb Fix Main CI use?

Frb Fix Main CI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Frb Fix Main CI use?

About 968 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Frb Fix Main CI?

Skills that share tags, products or a category with Frb Fix Main CI: Puremusic (qingyueyin/Pure-music, 188 stars), Core API Change (libnativeapi/nativeapi, 166 stars), Winapp CLI (boshi-xixixi/TraeSkill, 276 stars) and Spec To Repo (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frb Fix Main CI?

fzyzcjy (a GitHub user) maintains it in fzyzcjy/flutter_rust_bridge, which has 5,446 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 10, 2026.

Source: fzyzcjy/flutter_rust_bridge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.