github-pr-triage

Fetch open GitHub pull requests, analyze each in background tasks, and generate a final report.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill github-pr-triage-gdsdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-triage
Source: https://github.com/GDSDN/kord-aios/tree/main/.opencode/skills/github-pr-triage
Command: npx skills add https://github.com/GDSDN/kord-aios --skill github-pr-triage-gdsdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious and time-consuming process of triaging GitHub Pull Requests, ensuring that each PR is analyzed efficiently and actionable insights are provided promptly.

Core Features & Use Cases

  • Automated PR Triage: Analyzes all open GitHub Pull Requests in a repository.
  • Streaming Results: Provides real-time updates as each PR is processed, rather than waiting for all to complete.
  • Background Task Execution: Each PR is processed as an independent background task for isolation and parallelism.
  • Conservative Auto-Closing: Identifies and closes PRs that meet specific, conservative criteria (e.g., duplicate changes, outdated features).
  • Comprehensive Reporting: Generates a final report summarizing the status of all PRs.
  • Use Case: A maintainer of a busy open-source project can use this Skill to quickly get an overview of all open PRs, identify those ready for merge, flag those needing review, and automatically close stale or redundant ones, significantly reducing manual overhead.

Quick Start

Run the github-pr-triage skill to analyze all open pull requests in the current repository.

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 pull request triage for a busy GitHub repository?

Automated pull request triage fetches all open GitHub PRs and launches independent background tasks for each, streaming real-time analysis results to reduce manual repository maintenance overhead.

Can I automatically close stale or redundant GitHub pull requests?

Conservative auto-closing logic identifies and closes eligible GitHub pull requests that meet specific criteria, such as duplicate changes or outdated features, to maintain repository health.

What is the best way to analyze multiple open pull requests in parallel?

Analyzing multiple open pull requests in parallel is handled by launching a dedicated background task for each PR, isolating the processing and streaming real-time feedback as each completes.

How do I get a comprehensive report of open pull request statuses?

A comprehensive report summarizing the status of all open pull requests is generated after the streaming analysis completes, providing a final overview of repository maintenance needs.

Does GitHub PR triage provide real-time feedback during code review analysis?

Real-time feedback is provided during GitHub PR triage by streaming analysis results as each background task finishes, rather than waiting for all pull requests to complete processing.