skills.rest
getty104
getty104COMMUNITY
Explore all skills by this author →
Website𝕏@getty104GitHub

triage-pr

Automate GitHub PR triage with conflict detection, fix plans, and labels.

4|1|Updated Feb 14, 2026
Search Tags:#github#merge conflicts#pr triage#ci workflow#label automation
One-click install
npx skills add https://github.com/getty104/claude-task-worker --skill triage-pr-getty104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-pr
Source: https://github.com/getty104/claude-task-worker/tree/main/plugin/skills/triage-pr
Command: npx skills add https://github.com/getty104/claude-task-worker --skill triage-pr-getty104

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of triaging a GitHub Pull Request (PR), detecting conflicts, generating a fix plan, and taking appropriate actions based on the analysis.

Core Features & Use Cases

  • Conflict Detection: Identifies merge conflicts with the target branch using GitHub commands.
  • Fix Plan Evaluation: Generates and evaluates a fix plan to address identified issues.
  • Action Taking: Adds labels based on the fix plan and PR status (e.g., cc-fix-onetime, cc-release-ready).
  • Use Case: Save time by automating the initial triage steps of PRs, ensuring that only conflict-free and ready-to-merge PRs move forward.

Quick Start

Triage a PR with number '123' using the triage-pr skill.

Frequently Asked Questions about triage-pr

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

FAQPage Schema
How do I automate GitHub PR triage for merge conflict detection?▼

Automate GitHub PR triage by using this skill to detect merge conflicts with the target branch, generate a fix plan, and apply appropriate status labels within your continuous integration workflow.

How can I automatically label pull requests based on release preparedness in CI?▼

Label pull requests for release preparedness by evaluating the generated fix plan and PR status, which automatically applies labels like cc-fix-onetime or cc-release-ready to indicate merge readiness.

Do I need to configure GitHub API access and labels before automating PR triage?▼

Yes, you need to set up GitHub API access and configure the appropriate labels in your repository in advance to allow the automated PR triage process to analyze conflicts and apply labels.

What is the best way to generate a fix plan for unresolved merge conflicts in GitHub?▼

Generate a fix plan for merge conflicts by running the triage skill, which identifies conflicts against the target branch using GitHub commands and evaluates a resolution strategy before taking action.

Can I use this PR triage automation to evaluate pull requests in a continuous integration workflow?▼

Yes, this PR triage automation is intended for continuous integration workflows to ensure only conflict-free and ready-to-merge pull requests move forward by automatically detecting issues and applying labels.

Why are my automated PR labels not applying correctly during conflict detection?▼

Automated PR labels may fail to apply if the required labels are not set up in your GitHub repository in advance or if the GitHub API access lacks the necessary permissions for label automation.

Related Skills

Explore More Software Engineering Skills→
zizzfizzixzizzfizzix

open-pr

Commit changes, open a draft pull request, and normalize labels via GitHub API.

Community
Intermediate
abustamamabustamam

ship

Automate release workflows by merging branches, running tests, and opening PRs.

Community
Advanced
LuminairPrimeLuminairPrime

pr-guardian

Monitor and resolve GitHub PR issues via CI/CD checks and merge conflict management.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate