maintainer-triage

Batch-triage node-redis pull requests and issues, then execute approved GitHub actions.

17.6k|2.0k|Updated Sep 14, 2010
One-click install
npx skills add https://github.com/redis/node-redis --skill maintainer-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintainer-triage
Source: https://github.com/redis/node-redis/tree/main/.agents/skills/maintainer-triage
Command: npx skills add https://github.com/redis/node-redis --skill maintainer-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the redis/node-redis repository face a steady stream of pull requests and issues that each require review, a verdict, and a follow-up GitHub action. Doing this one-by-one by hand is slow and inconsistent, and mistakes like merging before CI passes or commenting unverified claims erode contributor trust.

Core Features & Use Cases

  • Filtered candidate gathering: Collect PRs or issues by timeframe, author, label, or search query via the GitHub CLI, automatically dropping items already merged or closed.
  • Parallel desk reviews: Fan out one subagent per item using the maintainer-review methodology, with pre-fetched metadata and diffs cached to disk to avoid repeated network calls.
  • One-at-a-time approval flow: Present each item with a one-word verdict (Merge, Revise, Supersede, Close, Evidence) plus a short summary, waiting for explicit user approval before acting.
  • Action execution with CI awareness: Post comments, submit formal reviews, approve gated fork CI runs, poll check-runs, and squash-merge only on green CI.
  • Use Case: Ask to triage all PRs opened in the last two weeks; the skill reviews each, walks you through verdicts one at a time, and merges, requests changes, or closes items as you approve.

Quick Start

Triage all open node-redis PRs from the past two weeks, review each one, and walk me through verdicts one at a time before taking any GitHub action.

Frequently Asked Questions about maintainer-triage

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

FAQPage Schema
How do I batch-triage GitHub pull requests as a maintainer?

Provide a filter such as timeframe, author, or label, and the skill lists matching PRs via the GitHub CLI, reviews each with the maintainer-review methodology, then presents verdicts one at a time. Approved actions like merge, request-changes, or close are executed per item.

How do I review multiple PRs by author or label on GitHub?

Use gh pr list with search filters for author, label, or date range to gather candidates. The skill caches each PR's metadata and diff to disk, then fans out parallel review subagents that produce structured verdicts without running tests or network calls.

Does this work with fork PRs that have gated CI runs?

Yes. Outside-contributor fork PRs create gated Actions runs with conclusion action_required. The skill finds them by head SHA via the GitHub API and approves each run before polling check-runs and merging only when CI is green.

Why does gh pr merge --auto merge immediately in this repository?

Auto-merge is disabled repo-wide and Actions CI is not a required check, so --auto merges instantly without waiting for CI. The skill instead polls check-runs every 30 seconds and merges only when no runs are failing or still running.

What permissions are needed to run GitHub maintainer actions?

The gh CLI must be authenticated with repo scope, and write commands like gh pr review, merge, close, and issue operations require allow-rules in settings. If a write is denied, the skill stops and asks the user to grant permission or run the command manually.