triage-contributor-pr

Triage external contributor pull requests on GitHub and produce evidence-backed verdicts.

47.6k|2.5k|Updated Jun 20, 2019
One-click install
npx skills add https://github.com/prisma/prisma --skill triage-contributor-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-contributor-pr
Source: https://github.com/prisma/prisma/tree/main/skills-contrib/triage-contributor-pr
Command: npx skills add https://github.com/prisma/prisma --skill triage-contributor-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of prisma/prisma face a queue of unsolicited pull requests from external contributors and must decide which are safe, in scope, and worth reviewing without accidentally running untrusted code or missing security risks.

Core Features & Use Cases

  • Queue Building and Snapshotting: Lists open fork PRs with the GitHub CLI, filters by author, and saves per-PR JSON and diff artifacts for offline analysis.
  • Safety and Security Sweep: Greps diffs for dangerous patterns (install scripts, child_process, pull_request_target, widened permissions) and audits workflow files before any CI approval.
  • Evidence-Based Verdicts: Verifies linked issues, DCO/CLA status, CI rollup states, version-line scope, direction fit, and staleness, then reports verdicts like Report, Close, Blocked on contributor, or Merge candidate.
  • Use Case: A maintainer asks to triage all open contributor PRs; the skill fetches each PR once, checks safety and mechanics, and returns a verdict table with file:line evidence and draft replies.

Quick Start

Triage the open external contributor pull requests on prisma/prisma and report a verdict with evidence for each one.

Frequently Asked Questions about triage-contributor-pr

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

FAQPage Schema
How do I triage external contributor pull requests on GitHub?

List open fork PRs with gh pr list filtered by isCrossRepository, save each PR's JSON and diff locally, then evaluate safety, linked issues, DCO/CLA, CI status, and scope. Report a verdict per PR with evidence such as file:line references and issue numbers.

How to check if a fork pull request is safe to run CI on?

Grep the diff for dangerous patterns like postinstall scripts, child_process, eval, pull_request_target, and secrets access, then audit all workflow files for widened permissions blocks or self-hosted runners. A clean grep is only a prompt to read the flagged files, not a verdict.

Can I run a contributor PR's tests locally to verify the fix?

No, running a fork PR's tests executes contributor-written code including install lifecycle scripts with your credentials and network access. Either run it in an isolated disposable container with no secrets, or report the test as unverifiable and rely on approved CI.

Why does a PR show only CodeRabbit or ACTION_REQUIRED in CI status?

Only CodeRabbit means the repository's CI has never run and needs maintainer approval, while ACTION_REQUIRED means a run is waiting for approval. Neither is a failure; only a FAILURE conclusion after reading which check failed counts against the contributor.

What are the limitations of automated PR triage for maintainers?

The skill is read-only: it reports verdicts and drafts replies but does not close PRs, post comments, or approve workflow runs. Approving CI and making direction calls on large features remain explicit maintainer decisions.