github-pr-triage

Triage GitHub PRs with one background task per PR and streamed results.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/vimalinx/VimaOS --skill github-pr-triage-vimalinx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-triage
Source: https://github.com/vimalinx/VimaOS/tree/main/oh-my-opencode/.opencode/skills/github-pr-triage
Command: npx skills add https://github.com/vimalinx/VimaOS --skill github-pr-triage-vimalinx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer, rich, and includes scripts (resource) components.

What problem does it solve?

GitHub PR triage can be slow and error-prone when manually evaluating every open PR. This skill automates the process by streaming analysis results and treating each PR as an isolated background task, enabling real-time decisions.

Core Features & Use Cases

  • Streaming PR analysis with one background task per PR for isolation and parallelism
  • Exhaustive PR collection using pagination to ensure no open PR is missed
  • Conservative auto-close of eligible PRs to reduce noise and focus maintainers
  • Final comprehensive triage report that summarizes readiness and recommended actions

Quick Start

Start the triage by fetching all open PRs, then launch a separate background task for each PR to analyze it and stream results in real time, followed by a final report.

Frequently Asked Questions about github-pr-triage

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

FAQPage Schema
How do I automate GitHub pull request triage for multiple open PRs?

GitHub pull request triage is automated by streaming analysis with a dedicated background task per PR. The workflow gathers all open PRs via pagination, launches isolated tasks for each, and streams real-time verdicts before producing a final comprehensive report.

How does streaming PR analysis work when reviewing open pull requests?

Streaming PR analysis works by assigning one background task to each open pull request and polling background_output for live results. This isolated parallel execution model provides real-time per-PR verdicts and conservatively auto-closes eligible PRs to reduce repository noise.

What is the best way to auto-close eligible pull requests while triaging a repository?

The best way to auto-close eligible pull requests during triage is to use a conservative automated workflow. After streaming per-PR analysis completes, the system evaluates readiness and conservatively closes qualifying PRs, outputting a structured triage verdict to guide maintainer actions.

Can I use background tasks to analyze GitHub pull requests in real time?

Yes, you can use background tasks to analyze GitHub pull requests in real time. The skill implements a strict 1 PR = 1 task pattern, launching separate background tasks that stream results through background_output polling as each PR is evaluated.

Do I need typer and rich to run automated pull request triage scripts?

Yes, you need typer and rich installed to run these automated pull request triage scripts. These dependencies provide the command-line interface framework and terminal formatting required to display the streaming real-time PR analysis results.

What are the limitations of using a strict 1 PR = 1 task pattern for GitHub PR analysis?

A limitation of the strict 1 PR = 1 task pattern for GitHub PR analysis is that launching separate background tasks for every open PR may hit rate limits or resource constraints on repositories with extremely high PR volumes, despite ensuring exhaustive no-PR-missed coverage.