pr-triage

Aggregate GitHub pull request CI status, review threads, and mergeability data.

Updated Apr 3, 2026

Search Tags:#automation #code review #pull request #github #triage #ci

Ready to run

npx skills add https://github.com/strawgate/agent-skills --skill pr-triage-strawgate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-triage
Source: https://github.com/strawgate/agent-skills/tree/main/pr-triage
Command: npx skills add https://github.com/strawgate/agent-skills --skill pr-triage-strawgate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This skill addresses the cognitive load and manual overhead of managing large volumes of open pull requests, ensuring that code reviews, CI status, and merge conflicts are handled systematically without human error.

Core Features & Use Cases

Automated Triage: Quickly audit open PRs to identify failing CI, merge conflicts, and unresolved review threads.
Merge Readiness: Generate comprehensive checklists to verify that a PR is safe to merge based on CI status and review completion.
Workflow Management: Claim and release PR ownership using visual indicators to prevent duplicate work among team members.

Quick Start

Use the pr-triage skill to audit all open pull requests for the repository strawgate/agent-skills and generate a merge readiness report for PR number 2664.

Frequently Asked Questions about 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 CI status and merge conflicts?▼

Automate GitHub pull request triage by aggregating CI status, review threads, and mergeability data to identify failing checks and merge conflicts. This skill fetches repository metadata via GitHub CLI to systematically audit open PRs without manual overhead.

How do I generate a merge readiness checklist for open pull requests?▼

Generate a merge readiness checklist by evaluating CI status, unresolved review threads, and mergeability data for a specific pull request. The skill creates structured checklists for maintainers to verify a PR is safe to merge based on current repository metadata.

Do I need GitHub CLI installed to automate PR review and triage workflows?▼

Yes, you need the GitHub CLI installed to automate PR review and triage workflows. The skill requires GitHub CLI integration to fetch repository metadata and perform safe, permission-gated pull request operations.

What's the best way to prevent duplicate work when managing multiple open pull requests?▼

Prevent duplicate work during pull request management by using visual indicators to claim and release PR ownership. The skill facilitates workflow management by tracking who is reviewing which PR, avoiding overlapping code review efforts among team members.

Can I use jq to parse and filter pull request metadata during automated triage?▼

Yes, jq is a required dependency for parsing and filtering pull request metadata during automated triage. The skill uses jq alongside GitHub CLI to process repository data and aggregate CI status, review threads, and mergeability information.

Why does automated PR triage fail when GitHub CLI permissions are insufficient?▼

Automated PR triage fails with insufficient GitHub CLI permissions because the skill performs safe, permission-gated pull request operations. It requires valid GitHub CLI authentication to fetch repository metadata, audit CI status, and execute merge readiness checks.