github-pr-triage

Fetch open GitHub PRs, analyze each in background tasks, and generate a triage report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious process of triaging GitHub Pull Requests, providing real-time analysis and intelligently suggesting or performing actions like auto-closing stale or redundant PRs.

Core Features & Use Cases

  • Real-time Streaming Analysis: Processes each PR in a dedicated background task and streams results as they complete, offering immediate insights.
  • Exhaustive PR Collection: Fetches all open PRs using robust pagination to ensure no PR is missed.
  • Conservative Auto-Closing: Identifies and closes PRs that are clearly redundant or outdated based on predefined criteria.
  • Comprehensive Reporting: Generates a final report summarizing the triage status of all PRs.
  • Use Case: A busy open-source project maintainer can use this Skill to get an immediate overview of all incoming PRs, identify those ready for merge, and automatically close old, irrelevant ones without manual intervention.

Quick Start

Use 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 triaging open GitHub pull requests?

Automate GitHub pull request triage by fetching all open PRs using the gh CLI, launching a dedicated background task for each PR to stream real-time analysis, and generating a final comprehensive status report.

Can I automatically close stale pull requests in my repository?

Yes, you can automatically close stale pull requests using a conservative auto-closing logic that identifies and closes PRs which are clearly redundant or outdated based on predefined criteria.

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

The best way to analyze multiple pull requests in parallel is a 1 PR = 1 background task architecture, which isolates processing and streams real-time analysis results as each task completes.

Does this pull request triage process require any specific CLI tools to run?

Yes, the pull request triage process requires the gh CLI for fetching repository data via pagination and bash commands for executing background tasks and streaming results.

How do I ensure no open pull requests are missed during automated triage?

To ensure no open pull requests are missed during automated triage, the process utilizes robust pagination when fetching all open PRs, guaranteeing exhaustive collection before analysis begins.

What limitations exist with conservative auto-closing for pull requests?

The limitation of conservative auto-closing is that it only targets pull requests that are clearly redundant or outdated, meaning borderline or active PRs are left untouched and require manual review.