parallel-pr-scope-overlap-tiebreaker-delta-check

Audits diffs of two scope-overlapping parallel PRs before applying merge tiebreaker rules.

3|Updated May 8, 2026
One-click install
npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill parallel-pr-scope-overlap-tiebreaker-delta-check-wan-huiyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel-pr-scope-overlap-tiebreaker-delta-check
Source: https://github.com/wan-huiyan/agent-traffic-control/tree/main/plugins/agent-traffic-control/skills/parallel-pr-scope-overlap-tiebreaker-delta-check
Command: npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill parallel-pr-scope-overlap-tiebreaker-delta-check-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When two parallel sessions open PRs targeting the same issue, handoff prompts often recommend a winner using merge-mechanics rules (first-mover, clean-against-main, single-reviewer APPROVE) that ignore implementation quality, silently shipping the inferior fix and losing substantive improvements. ## Core Features & Use Cases - Pre-Tiebreaker Delta Audit: Runs gh pr diff on both PRs and classifies each delta as substantive (new error paths, validation, different semantics) or cosmetic (naming, whitespace, comments) before accepting any tiebreaker default. - Stale-State Refresh: Re-polls gh pr view --json state,mergeable,statusCheckRollup to detect already-merged PRs via post-merge workflow signals before deciding. - Override & Documentation Workflow: Surfaces override decisions to the user in auto-mode, closes the loser with neutral coordination framing, and records the deltas in MEMORY.md and tracker entries. - Deployed-Fix Variant: Handles the case where one fix is already live by establishing ground truth from the deployed artifact and reconciling via an atomic swap instead of a blind deploy. - Use Case: A handoff prompt says "merge PR #542, it's first-mover and clean"; you diff both PRs, find the later PR #553 has a real correctness fix, and override the default to ship the better implementation. ## Quick Start Ask the AI to compare the diffs of the two parallel PRs for the same issue and verify which implementation is substantively better before merging the one the handoff prompt recommended.

Frequently Asked Questions about parallel-pr-scope-overlap-tiebreaker-delta-check

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

FAQPage Schema
How do I choose between two parallel PRs fixing the same issue?▼

Run gh pr diff on both PRs and classify each delta as substantive (new error paths, validation, semantic changes) or cosmetic (naming, whitespace). Merge the PR with substantive improvements rather than relying on first-mover or clean-against-main rules.

Why is merging the first-mover PR a risky tiebreaker?▼

First-mover, clean-against-main, and single-reviewer-APPROVE rules optimize for merge mechanics, not correctness. The later PR often contains refined implementations, defensive validation, or multi-reviewer fixups that the earlier one lacks.

How can I tell if a GitHub PR has already merged?▼

Re-poll gh pr view --json state,mergeable,statusCheckRollup. A state of MERGED is definitive, and post-merge workflow names like Deploy or Auto-deploy in statusCheckRollup indicate the PR already merged, since those fire on pull_request closed events.

What should I do when a competing fix is already deployed live?▼

Establish ground truth from the live deployed artifact, not from main or your branch, by grepping the deployed file for each fix's distinctive markers. Then reconcile via an atomic swap: revert the live fix and deploy the winner as one change, never blind-deploy over it.

When is it safe to skip the parallel PR delta check?▼

The check exists to falsify equivalence, so if both diffs prove substantively identical, the prompt's default tiebreaker is fine. The audit costs about five minutes, while skipping it can lose correctness fixes that take weeks to re-implement.