parallel-pr-template-fork-duplicates-moved-section SKILL.md skillA
parallel-pr-template-fork-duplicates-moved-section 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-template-fork-duplicates-moved-section@v1.0.0Pins v1.0.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-template-fork-duplicates-moved-section/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 12,639 bytes
- Repository stars
- 3
- License
- MIT
Diagnose silent semantic duplication after two parallel PRs ship. Use when: (1) one PR (the **mover**) relocates a section/component/block from template X to template Y (X loses it, Y gains it), (2) a sibling PR (the **forker**), authored against pre-mover main, creates / promotes / copies template Z from the OLD version of X (when X still contained the section), (3) both PRs squash-merge without textual conflict because they touch different files, (4) after both deploy, the section appears on…
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
# Parallel-PR Template Fork Duplicates Moved Section ## Problem Two PRs ship within hours of each other. Neither shows a textual merge conflict. Both pass tests. Both deploy cleanly. After deploy, a user reports "this section is appearing in two places now — that's wrong, right?" The mechanism is structural, not textual: - **PR #A (mover)**: relocates a `<section>...</section>` from template `X.html` to template `Y.html`. `X` loses the block; `Y` gains it. - **PR #B (forker)**: promotes / copies / forks `X.html` into a new template `Z.html` (e.g., the route is moving up in the IA, or the page is being split). The fork is literal — `Z.html` was authored as a near-copy of `X.html` *as it existed before the mover landed*. - The two PRs touch *different files* on disk. Squash-merge is "clean" by git's textual measure: `X` lost a block (mover), `Y` gained it (mover), `Z` was added (forker). No 3-way merge conflict. - Reality: `Z` was forked from a snapshot of `X` that *still contained* the section. So after both ship, the block lives in BOTH `Y` and `Z`. The user sees the duplication immediately. Code review on each PR in isolation …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/parallel-pr-template-fork-duplicates-moved-section@sha256:2d29b364626c2de6The line at the top of this page pins the label v1.0.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_qt3tkvt445ta5tvu)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 13, 2026 and Aug 11, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 12,639 B | A | view · diff |
| v1.0.0 | 2026-08-05 | e3930cf | 12,654 B | A | view · diff |
| v1.0.0 | 2026-07-08 | b0f0d02 | 13,208 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 13,212 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 13,181 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 (12639 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_qt3tkvt445ta5tvu GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/parallel-pr-template-fork-duplicates-moved-section GET https://markdownregistry.com/api/v1/blob/2d29b364626c2de6eeddba173cf290caef7a79056ca258b7fc37de6460298736
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.