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 Issue To Green PR

by fzyzcjy in fzyzcjy/flutter_rust_bridge

A skill your agent uses when implementing a GitHub issue, bug fix, or feature in flutterrustbridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's…

MITAuto-check passedDevelopment

Install Frb Issue To Green PR

skills CLI
$ npx skills add fzyzcjy/flutter_rust_bridge --skill frb-issue-to-green-pr -a claude-code

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

GitHub CLI
$ gh skill install fzyzcjy/flutter_rust_bridge frb-issue-to-green-pr --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-issue-to-green-pr .claude/skills/frb-issue-to-green-pr && 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-issue-to-green-pr
GitHub stars
5.4k
Token cost
~1.8k tokens
SKILL.md length
1,042 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementing a GitHub issue, bug fix, or feature in flutterrustbridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's…

  • Works in 8 steps: Start the completion loop → Understand the GitHub issue or requested… → Reproduce the issue in an independent… → …
  • Implementing a GitHub issue
  • SKILL.md covers Required Subskills, Workflow, Automation Rules and Failure Handling
  • Calls git

What it does

Frb Issue To Green PR is an agent skill from fzyzcjy/flutter_rust_bridge. Use when implementing a GitHub issue, bug fix, or feature in flutterrustbridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's tom-ci skill to monitor CI until the PR is ready.

Its SKILL.md is about 1.8k 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 Development, covering Cross-platform mobile apps, Debugging and Pull requests. It works with GitHub, Rust and Flutter. 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

  • Implementing a GitHub issue
  • Feature in flutterrustbridge end-to-end: develop the change
  • Add regression coverage
  • Prepare and open a PR

Example prompts

  • “/frb-issue-to-green-pr”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Start the completion loop
  2. Understand the GitHub issue or requested change
  3. Reproduce the issue in an independent reproduction PR
  4. Fix the issue
  5. Prepare and open the PR
  6. Run the review gate
  7. Monitor CI until terminal
  8. Stop only when ready

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 Issue To Green PR loads about 1.8k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,042 words of instructions outside code blocks.

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

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). 1,042 words, ~1,785 tokens.

Download SKILL.mdSave it as .claude/skills/frb-issue-to-green-pr/SKILL.md (or your agent's skills folder).
name
frb-issue-to-green-pr
description
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, and use the user's tom-ci skill to monitor CI until the PR is ready.

FRB Issue to Green PR

Use this skill as the top-level workflow when the user asks you to implement an issue, fix a bug, add a feature, or otherwise "handle it end to end" in flutter_rust_bridge, especially when they ask for an automatic PR or CI monitoring.

This skill orchestrates the narrower FRB skills. Do not duplicate their detailed instructions in memory; read them when their phase begins.

Required Subskills

Always read these first:

  1. frb-dev-env and any applicable user-level environment rules.
  2. frb-develop-feature for the reproduce -> fix -> final regression workflow.

Read these when entering the matching phase:

  • frb-code-generation before running generation or changing Rust APIs, codegen, or example APIs.
  • frb-test before running local tests.
  • frb-lint before lint or format checks.
  • frb-prepare-pr before pushing or opening the PR.
  • frb-pr-review before treating a non-trivial PR as ready.
  • frb-fix-ci before diagnosing any CI failure.
  • The user's tom-ci skill for CI waiting, status inspection, and GitHub Actions logs.
  • frb-manual-test before writing a manual regression test report under tools/manual_tests/.
  • frb-ci-filter before creating an intentional red CI reproduction PR or using filtered CI.
  • frb-debugging when generated code is surprising or codegen behavior is unclear.

Workflow

1. Start the completion loop
  • Keep the task active until all stop conditions are met.
  • Once the PR URL is known, follow the waiting workflow in the user's tom-ci skill between CI processing actions until the PR is ready.
2. Understand the GitHub issue or requested change
  • Fetch the issue body and comments if the user gave an issue link or number.
  • Identify the smallest observable failing behavior or missing capability.
  • Check git status --short and do not disturb unrelated user or multi-agent changes.
3. Reproduce the issue in an independent reproduction PR
  • Read and follow the reproduction parts of frb-develop-feature.
  • For bug fixes, do this before changing fix code or opening the fix PR.
  • Create an independent reproduction PR whose only purpose is to prove the bad behavior. The branch name, PR title, and PR body must say clearly that it is an intentional reproduction PR, not a real fix PR.
  • For intentional red CI reproduction PRs, use the title Reproduce ISSUE_SUMMARY with intentional red CI.
  • For manual-test reproduction PRs, use the title Add manual reproduction for ISSUE_SUMMARY.
  • If CI can reproduce the bad behavior, read frb-ci-filter and make the reproduction PR an intentional red CI PR: unchanged fix code, minimal reproducer or workflow adjustment, mandatory focused ci_filter run, and a failure whose error matches the user's report.
  • If CI cannot realistically reproduce the bad behavior, read frb-manual-test and make the independent reproduction PR add or update tools/manual_tests/NAME.md with a normal manual test procedure and mechanical execution steps an agent or human can run.
  • Do not proceed to the fix PR until the reproduction PR exists and has either a matching red CI run or a precise manual test report.
  • Save the reproduction PR URL, red CI run URL when applicable, job name or manual-test path, and matching error text for the fix PR reproduction report.
4. Fix the issue
  • Read and follow the fix, iteration, local verification, regression coverage, and final placement parts of frb-develop-feature.
  • Implement the smallest change that fixes the reproduced behavior.
  • Add final regression coverage with the fixed behavior as the expected result.
  • Make atomic commits as soon as each completed logical unit is written; do not wait until the end of the task.
  • Stage only files intentionally changed for this task.
  • Always create a new commit unless the user explicitly asks to amend.
  • Before considering the change ready, explicitly pass the frb-develop-feature Final Placement Gate: final regression coverage belongs in frb_example/pure_dart with generated pure_dart_pde coverage, not only in frb_example/dart_minimal.
  • Keep generated-file edits produced by the appropriate generator, not by hand.
Show full SKILL.md (426 more words)Show less
5. Prepare and open the PR
  • Follow frb-prepare-pr.
  • Re-check that no final regression or feature coverage remains only in frb_example/dart_minimal. If it does, stop PR preparation and migrate it to frb_example/pure_dart first.
  • Push with upstream tracking.
  • Before drafting a PR title, inspect the user's recent PR titles and mimic the repo style.
  • Create the PR according to the active PR workflow and repository/user PR body rules.
  • If the work comes from a GitHub issue, ensure the PR body includes the appropriate closing keyword such as Close #1234, unless the active PR workflow explicitly requires an empty body.
6. Run the review gate
  • Follow frb-pr-review for the full PR review gate, including correctness review and test-weakening review.
7. Monitor CI until terminal
  • After the PR is opened or updated, do not leave the PR in an unknown queued or in-progress state.
  • On each wake-up, inspect the latest PR checks, not stale runs.
  • For bug-fix PRs with an intentional red CI reproduction PR, explicitly find the same job family or CI path that failed in the reproduction branch and verify that it is now green on the fix PR.
  • For bug-fix PRs with a manual-test report PR, state whether the manual regression was re-run, who or what ran it, and whether the observed behavior now matches the fixed expectation.
  • If CI fails, read frb-fix-ci and the user's tom-ci skill, diagnose the latest relevant failure, fix it, commit, push, and continue monitoring.
  • If CI appears flaky, rerun only failed jobs when appropriate, then keep monitoring.
8. Stop only when ready
  • The PR checks are green or all remaining non-green checks are clearly unrelated and explained.
  • The branch is pushed, commits are present on the PR, and the final status is reported to the user with the PR URL.

Automation Rules

  • Follow the user's tom-ci skill to wait on the PR URL after each push, rerun, or handled CI event.
  • Treat its return as a wake-up signal, not a CI verdict. Inspect the reported checks, fix or rerun as required, then call the waiter again.
  • Do not add a separate time-based heartbeat or detached polling loop for the same PR.
  • Stop invoking the waiter once the stop conditions are met.

Failure Handling

  • If blocked by permissions, missing credentials, a required external reviewer delay, or unavailable infrastructure, explain the concrete blocker and keep the PR state explicit.
  • If a CI run is queued for a long time, continue bounded waits using the user's tom-ci skill.
  • If new user instructions arrive, let the newest instruction steer the workflow while preserving already-completed work.

© 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-issue-to-green-pr of fzyzcjy/flutter_rust_bridge.

Open the folder on GitHubat commit 848e438

Compare with similar skills

Frb Issue To Green PR 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 Issue To Green PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frb Issue To Green PR this skillfzyzcjy/flutter_rust_bridge5.4k—~1.8kAutomated safety check: PassMIT
Grix Code Reviewaskie/grix153—~799Automated safety check: PassCustom licence
Winapp CLIboshi-xixixi/TraeSkill276—~1.9kAutomated safety check: PassMIT
Review PRhyochan/flutter_calendar_carousel860—~1.4kAutomated safety check: PassMIT
MCP Debuggerdebugmcp/mcp-debugger174—~4.2kAutomated safety check: PassMIT
.NET MAUI Code Reviewdotnet/efcore15k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Grix Code Review

    askie/grix

    Audit Grix diffs and pull requests for correctness, regressions, security, lifecycle safety, and cross-component contract consistency.

    153 GitHub stars~799 tokensUpdated today
    DevelopmentAuto-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

  • Review PR

    hyochan/flutter_calendar_carousel

    Inspect and finish fluttercalendarcarousel pull requests by fixing valid review findings, replying and resolving threads, diagnosing CI, using review-self when automation is unavailable, and polling…

    860 GitHub stars~1.4k tokensUpdated 20 days ago
    DevelopmentAuto-check passed

  • MCP Debugger

    debugmcp/mcp-debugger

    A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…

    174 GitHub stars~4.2k tokensUpdated today
    DevelopmentAuto-check passed

  • .NET MAUI Code Review

    dotnet/efcore

    Official

    Deep code-only review of a pull request or candidate patch for correctness, safety and .NET MAUI conventions, judging the code before reading the PR description.

    15k GitHub stars~2.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Reviewing Devtools PRs

    flutter/devtools

    DevTools repository-specific PR review workflow enforcing DevTools style guidelines and common review patterns.

    1.7k GitHub stars~638 tokensUpdated 3 days ago
    DevelopmentAuto-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 Issue To Green PR

What does Frb Issue To Green PR do?

A skill your agent uses when implementing a GitHub issue, bug fix, or feature in flutterrustbridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's…. Frb Issue To Green PR is an agent skill from fzyzcjy/flutter_rust_bridge. Use when implementing a GitHub issue, bug fix, or feature in flutterrustbridge end-to-end: develop the change, add regression coverage, prepare and open a PR, and use the user's tom-ci skill to monitor CI until the PR is ready.

When should I use Frb Issue To Green PR?

Frb Issue To Green PR fits situations like: implementing a GitHub issue; feature in flutterrustbridge end-to-end: develop the change; add regression coverage; prepare and open a PR.

How do I install Frb Issue To Green PR in Claude Code?

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

How do I install Frb Issue To Green PR in Codex?

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

Can I use Frb Issue To Green PR 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-issue-to-green-pr -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-issue-to-green-pr, .gemini/skills/frb-issue-to-green-pr, .github/skills/frb-issue-to-green-pr and .opencode/skills/frb-issue-to-green-pr in your project.

What does Frb Issue To Green PR need to run?

Going by SKILL.md and its folder, Frb Issue To Green PR needs the command-line tools its instructions call (git).

Does Frb Issue To Green PR 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 Issue To Green PR 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 Issue To Green PR use?

Frb Issue To Green PR 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 Issue To Green PR use?

About 1.8k tokens (SKILL.md is roughly 7.1k 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 Issue To Green PR?

Skills that share tags, products or a category with Frb Issue To Green PR: Grix Code Review (askie/grix, 153 stars), Winapp CLI (boshi-xixixi/TraeSkill, 276 stars), Review PR (hyochan/flutter_calendar_carousel, 860 stars) and MCP Debugger (debugmcp/mcp-debugger, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frb Issue To Green PR?

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.