competing-pr-triage

Name: competing-pr-triage
Availability: InStock
Author: jackzhaojin

Compare two competing PRs and output a branch recommendation with follow-up plan.

1|Updated Mar 22, 2026

Search Tags:#multi-agent #triage #code-review #decision-making #pull-request #parallel-worktrees

Ready to run

npx skills add https://github.com/jackzhaojin/ai-builder-kit --skill competing-pr-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: competing-pr-triage
Source: https://github.com/jackzhaojin/ai-builder-kit/tree/main/skills/competing-pr-triage
Command: npx skills add https://github.com/jackzhaojin/ai-builder-kit --skill competing-pr-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triage two competing PRs to determine which should be adopted.

Core Features & Use Cases

Systematically compare two PR diffs, map changes to a goal's requirements, and surface gaps.
Produce a structured four-part report: functional requirements table, file-level scope audit, non-functional aspects, and a closing verdict with follow-up steps.
Provide precise switch-and-follow-up instructions for next actions after selecting a winner.

Quick Start

Provide a structured triage report by comparing two PRs and output a decision along with a follow-up plan.

Frequently Asked Questions about competing-pr-triage

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

FAQPage Schema

How do I decide which pull request to merge when two branches solve the same goal?▼

To decide which pull request to merge, you can triage competing branches by verifying changes against goal requirements and performing a file-level scope audit. This produces a structured report with a merge verdict and a concrete follow-up plan.

What is the best way to compare code diffs from parallel worktrees?▼

Comparing code diffs from parallel worktrees is best handled by systematically mapping changes to functional requirements and auditing non-functional aspects. This surfaces gaps between branches and provides a structured recommendation for which diff to adopt.

How do I review multiple agent pull requests when branches solve the same feature?▼

Reviewing multiple agent pull requests involves triaging competing branches to determine which should be adopted. The process maps changes to a goal's requirements, audits file-level scope, and outputs a branch recommendation with switch-and-follow-up instructions.

What does a pull request triage report include for competing branches?▼

A pull request triage report for competing branches includes a functional requirements table, a file-level scope audit, non-functional aspects analysis, and a closing verdict. It also provides precise switch-and-follow-up instructions for next actions after selecting a winner.

Can I use code review triage for multi-agent parallel branch scenarios?▼

Yes, you can use code review triage for multi-agent parallel branch scenarios where different branches solve the same goal. It is specifically designed to verify changes against requirements and provide a decision on merge or continuation.