Install any skill in seconds. Free to start, no credit card required.
Get Started Free →flutter/shepherd-prs
Automate shepherding, checking status, updating branches, and landing open PRs or approved third-party contributor PRs in the flutter/flutter repository using the gh CLI. When to use: - When you need to check the status of open PRs or shepherded third-party PRs. - When you need to update stale branches or apply the 'autosubmit' label to land approved PRs. When not to use: -
Passed 10 of 15 test cases with the skill, and 9 of 15 without it.
and 1 more in the full report
3 fixed12 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am evaluating PR #149000 in flutter/flutter for landing. The PR was last updated 10 days ago and its base commit is over a week old. All CI checks were passing previously. Should I add the autosubmit label immediately?
| Checked | Without skill | With skill |
|---|---|---|
| Advises against adding autosubmit before updating the branch. | Passed | Passed |
| Recommends updating the branch via gh pr update-branch. | Missed | Passed |
The instructions your model reads when the skill loads.
flutter/flutter)This skill defines the canonical runbook for shepherding pull requests in the flutter/flutter repository using native GitHub CLI (gh) commands.
When the user asks for the status of open or approved PRs:
gh pr list --repo flutter/flutter --author <username> --state open --json number,title,url,mergeable,reviewDecision
gh pr list --repo flutter/flutter --search "reviewed-by:<username> -author:<username> is:open" --json number,title,url,mergeable,reviewDecision
gh pr checks <number> --repo flutter/flutter
gh pr view <number> --repo flutter/flutter --json labels,reviewDecision,reviews,comments
Before applying or re-applying the autosubmit label (gh pr edit <number> --repo flutter/flutter --add-label autosubmit), always perform the following pre-flight verification checks to ensure the autosubmit bot will not reject or strip the label:
Check Previous autosubmit Removal History in Comments:
autosubmit label was previously removed by the auto-submit bot by checking PR comments:
gh pr view <number> --repo flutter/flutter --json comments
auto-submit such as "autosubmit label was removed...".autosubmit.Verify Freshness of Base Commit (>7 Days Old):
autosubmit:
test cases passed, vs 9 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.