create-contributor-prs

Dispatches the sync-and-rebase workflow to create in-org draft PRs for external contributor pull requests.

3.6k|1.4k|Updated Nov 10, 2017
One-click install
npx skills add https://github.com/brave/brave-core --skill create-contributor-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-contributor-prs
Source: https://github.com/brave/brave-core/tree/main/agents/skills/create-contributor-prs
Command: npx skills add https://github.com/brave/brave-core --skill create-contributor-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External contributors fork brave/brave-core and open PRs from their forks, but most of Brave's CI does not run on fork PRs for security reasons. This Skill dispatches the sync-and-rebase-pr-from-fork.yml workflow so an in-org mirror branch and draft PR are created, letting full CI run on the contributor's rebased commit.

Core Features & Use Cases

  • PR Resolution: Accepts a GitHub username, PR numbers, short forms like #36402, or full PR URLs, and resolves them to open cross-repo PRs against brave/brave-core.
  • Duplicate Dispatch Detection: Reads recent workflow run logs to extract the COMMIT_HASH input and skips PRs whose current HEAD SHA was already dispatched.
  • Safe Filtering and Confirmation: Skips non-cross-repo and closed PRs, and asks for confirmation before batch dispatching since each run consumes CI minutes.
  • Use Case: A maintainer says "create contributor PRs for jharris-tech" and the Skill finds all their open fork PRs, checks which HEAD commits already have dispatched runs, dispatches the workflow only where needed, and reports a per-PR status table.

Quick Start

Ask the assistant to create contributor PRs for a GitHub username or a list of brave/brave-core PR numbers so the rebase-from-fork workflow runs for each one.

Frequently Asked Questions about create-contributor-prs

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

FAQPage Schema
How do I run CI on a fork pull request in brave/brave-core?

Dispatch the sync-and-rebase-pr-from-fork.yml workflow with the PR number and its HEAD commit SHA. The workflow rebases the fork commit onto the base branch, force-pushes a contributor branch, and opens a draft PR that triggers full CI.

How do I create contributor PRs for all open PRs by a GitHub user?

Provide the GitHub username and the Skill lists their open PRs against brave/brave-core using gh pr list, filters to cross-repo PRs, and dispatches the workflow for each HEAD commit not already dispatched.

Why does the sync-and-rebase-pr-from-fork workflow fail for some PRs?

The workflow exits with an error for same-repo PRs because it requires isCrossRepository to be true. The Skill filters these out client-side before dispatching, along with closed or merged PRs.

How do I check if the rebase workflow already ran for a PR commit?

GitHub does not expose workflow_dispatch inputs via the runs API, so you must read the run's job log and grep for the COMMIT_HASH line. Compare that SHA against the PR's headRefOid to detect prior dispatches.

What happens if the workflow is dispatched twice for the same commit?

The workflow is idempotent: it force-pushes the same contributor branch and skips creating a draft PR if one already exists. A duplicate dispatch wastes CI minutes but causes no destructive changes.