Frb Add Contributor
Productivityfrb-add-contributorFrb Add Contributor is an Agent Skill for productivity published in the fzyzcjy/flutter_rust_bridge repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Add or reconcile flutter_rust_bridge contributors through all-contributors PRs. Use when finding contributor PRs, posting all-contributors comments, validating contributor metadata, resolving contributor PR merge conflicts, or merging the generated contributor PRs.
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-add-contributor/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/frb-add-contributor, 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 Add Contributor
Use this skill when contributors need to be added to flutter_rust_bridge via all-contributors, especially when multiple recent PR authors should be credited in batch.
Step 1: Find the correct source PRs
For each GitHub username, find their PRs in fzyzcjy/flutter_rust_bridge.
gh search prs --repo fzyzcjy/flutter_rust_bridge --author <username> --limit 100 --json number,title,author,url,state
Important:
- Deduplicate by contributor. A single person may have multiple merged PRs.
- If the task is about
new contributor PRs, use the contributor's first PR only. - If the contributor already exists in
.all-contributorsrcorREADME.md, do not expect a new all-contributors PR to be created.
Step 2: Stop for human confirmation
After determining which contributors may need to be added, stop and ask a human to confirm the contributor list and source PRs before taking any mutating action.
This stop is mandatory.
- Do not edit
.all-contributors-custom.yaml. - Do not regenerate contributor artifacts.
- Do not post all-contributors comments.
- Do not create or merge any PRs.
- Do not perform any other GitHub mutation.
Only continue after the human explicitly confirms which contributors to add and which source PRs to use.
Step 3: Prepare .all-contributors-custom.yaml and stop for human input
Before regenerating contributor artifacts, append each new contributor to the end of .all-contributors-custom.yaml:
- <username>: TODO
Do this only for contributors who are not already present in .all-contributors-custom.yaml.
Then stop and ask a human to replace each TODO with a concise contribution summary.
This stop is mandatory.
- Do not continue to Step 3 or any later step in this skill until the human has replaced every
TODO. - Do not run contributor generation.
- Do not post all-contributors comments.
- Do not resolve or merge contributor PRs.
Only resume after the human-written descriptions are present in .all-contributors-custom.yaml.
Step 4: Trigger all-contributors
Post the comment on the chosen source PR:
gh pr comment <pr-number> --repo fzyzcjy/flutter_rust_bridge --body '@all-contributors please add <username> for code'
Then inspect the bot response on that PR.
- If the bot says the user already contributed before, stop there for that user.
- Otherwise, wait for the bot to open a PR named
docs: add <username> as a contributor for code.
Step 5: Validate contributor metadata
When a contributor PR exists, check the generated contributor data before merging.
Files to inspect:
.all-contributorsrcREADME.md
Required validation:
- Homepage URLs must use
https://, neverhttp://. - If the generated homepage is
http://, change it tohttps://if the site supports it. - If the personal site does not support
https://, prefer the contributor's GitHub profile URL instead of keepinghttp://.
Step 6: Regenerate contributor output
After the human has replaced all TODO messages, regenerate the contributor artifacts instead of hand-editing README.md.
Use:
./frb_internal generate-internal-contributor
This command updates:
.all-contributorsrcREADME.mdviaall-contributors generatewebsite/docs/index.mdviagenerate-internal-readme
If you only need to refresh the website copy of the README, use:
./frb_internal generate-internal-readme
Step 7: Resolve merge conflicts in contributor PRs
These PRs usually conflict only in:
.all-contributorsrcREADME.md
Recommended workflow for each open contributor PR:
gh pr checkout <pr-number> --repo fzyzcjy/flutter_rust_bridge
git fetch origin master
git merge --no-ff origin/master
If the merge conflicts:
- Keep the latest
origin/mastercontent. - Re-apply the contributor entry from the bot branch.
- Ensure the contributor card remains present in
README.md. - Re-run
./frb_internal generate-internal-contributorif you edited contributor metadata or finished filling in.all-contributors-custom.yaml. git addthe resolved files and commit the merge.- Push the contributor branch back to origin.
Do not revert unrelated contributor entries that were merged by other PRs.
Step 8: Merge the contributor PRs
After the branch is updated and GitHub reports it mergeable:
gh pr merge <pr-number> --repo fzyzcjy/flutter_rust_bridge --merge --delete-branch
Notes:
- GitHub may temporarily report
DIRTYor reject merge immediately after push. - If that happens, wait briefly, re-check the PR state, and retry the merge.
- After merging one contributor PR, fetch
origin/masteragain before resolving the next one.
Step 9: Final verification
At the end, verify there are no remaining open all-contributors PRs:
gh pr list --repo fzyzcjy/flutter_rust_bridge --search "author:allcontributors[bot] is:open" --limit 50 --json number,title,mergeStateStatus,url
Also verify the credited contributors appear in:
.all-contributorsrcREADME.mdwebsite/docs/index.mdif contributor regeneration was run