shepherd-prs

Automate checking, updating, and landing pull requests in the flutter/flutter repository.

179k|31.0k|Updated Mar 6, 2015
One-click install
npx skills add https://github.com/flutter/flutter --skill shepherd-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shepherd-prs
Source: https://github.com/flutter/flutter/tree/main/.agents/skills/shepherd-prs
Command: npx skills add https://github.com/flutter/flutter --skill shepherd-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing open pull requests in the flutter/flutter repository requires constant monitoring of CI status, branch freshness, reviewer approvals, and autosubmit bot behavior. This Skill provides a canonical runbook to automate these checks and safely land approved PRs.

Core Features & Use Cases

  • PR Status Inspection: List your own open PRs or shepherded third-party PRs, and inspect detailed checks, reviews, and labels.
  • Pre-Autosubmit Verification: Validate that the base commit is fresh, all CI checks pass, and at least two team member approvals exist before applying the autosubmit label.
  • Branch and Label Management: Update stale branches, re-apply the CICD label after updates, and handle merge conflicts or token scope errors.
  • Use Case: A Flutter team member wants to land a third-party contributor PR. Use this Skill to verify two team approvals, confirm CI is green, update the branch, and apply the autosubmit label so the bot merges it automatically.

Quick Start

Use the shepherd-prs skill to check the status of my open pull requests in flutter/flutter and tell me which ones are ready for autosubmit.

Frequently Asked Questions about shepherd-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of my open pull requests in flutter/flutter?

Run gh pr list --repo flutter/flutter --author <username> --state open --json number,title,url,mergeable,reviewDecision. This returns your open PRs with their mergeable state and review decision for quick triage.

How to apply the autosubmit label to a pull request safely?

Before applying autosubmit, verify all CI checks pass, the base commit is less than 7 days old, and third-party PRs have at least 2 team member approvals. Then run gh pr edit <number> --repo flutter/flutter --add-label autosubmit.

Why does the autosubmit bot remove the autosubmit label from my PR?

The auto-submit bot strips the label when CI checks fail, the branch is stale, or third-party PRs lack two team member approvals. Check PR comments for the exact reason and resolve it before re-applying the label.

How do I update a stale pull request branch in flutter/flutter?

Run gh pr update-branch <number> --repo flutter/flutter to rebase the PR onto master. After updating, re-apply the CICD label with gh pr edit <number> --add-label CICD to trigger CI on the new commit.

Can I re-run failing LUCI checks via the GitHub CLI?

No, third-party LUCI checks created by flutter-dashboard cannot be re-run via the GitHub API due to permission policies. Open the Buildbucket URL from the failing check and click Retry Build manually on the LUCI page.

When should I not use the shepherd-prs skill?

Do not use this skill for unapproved pull requests unless they are your own and you only want a status check. It is also restricted to the flutter/flutter repository and does not apply to other GitHub projects.