parallel-pr-scope-overlap-tiebreaker-delta-check SKILL.md skillA
parallel-pr-scope-overlap-tiebreaker-delta-check from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/parallel-pr-scope-overlap-tiebreaker-delta-check@v1.1.0Pins v1.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/parallel-pr-scope-overlap-tiebreaker-delta-check/SKILL.md- Versions recorded
- 4
- Latest version
- v1.1.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 14,699 bytes
- Repository stars
- 3
- License
- MIT
Before applying a handoff prompt's tiebreaker default ("merge the first-mover", "the clean-against-main one", "the one with reviewer APPROVE") to pick a winner between two parallel PRs that implemented the SAME scope, run `gh pr diff` on BOTH and audit for substantive deltas. Use when: (1) a session prompt or handoff doc surfaces a parallel-PR collision and recommends a tiebreaker, (2) two PRs targeting the same issue / same fix area are open simultaneously authored by different sessions, (3)…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pre-Tiebreaker Delta Check on Scope-Overlapping Parallel PRs
## Problem
Two parallel sessions independently opened PRs targeting the same issue
(same fix scope, same files, same goal). A session-handoff prompt later
asks a third session to pick a winner. The prompt's recommended tiebreaker
is some combination of:
- "Merge the first-mover" (older PR by createdAt)
- "Merge the one that's clean against main" (mergeable: CLEAN, no rebase needed)
- "Merge the one with reviewer APPROVE" (assumed implies higher quality)
- "Merge the one with wider scope" (e.g., bundles verification + handoff doc)
These rules are about **merge mechanics**, not implementation quality.
They can — and do — ship the inferior PR while the better implementation
gets closed.
## Trigger Conditions
ALL of the following must hold:
1. Two parallel PRs are open simultaneously, targeting overlapping scope
(same issue number cited as `Closes #N`; same files touched; same fix
intent).
2. A session-handoff prompt explicitly suggests a tiebreaker default
("merge #X because it's first-mover", "clean against main", "wider
scope"), or you're operating from such instructions in auto-mode.
…Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/parallel-pr-scope-overlap-tiebreaker-delta-check@sha256:03acd60927d39834The line at the top of this page pins the label v1.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4l2vnz3zczjdovp5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-08-11 | f274e4b | 14,699 B | A | view · diff |
| v1.1.0 | 2026-08-05 | e3930cf | 14,700 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 14,840 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 13,259 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14699 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4l2vnz3zczjdovp5 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/parallel-pr-scope-overlap-tiebreaker-delta-check GET https://markdownregistry.com/api/v1/blob/03acd60927d398341f7af96a96a4351d6cbebc54ac33a1c7ba52005d2fe7c41d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.