gha-pr-merge-ref-shows-upstream-changes SKILL.md skillA
gha-pr-merge-ref-shows-upstream-changes 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/gha-pr-merge-ref-shows-upstream-changes@v1.0.1Pins v1.0.1 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/gha-pr-merge-ref-shows-upstream-changes/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.1, committed Aug 12, 2026
- First version recorded
- May 13, 2026
- Size
- 9,509 bytes
- Repository stars
- 3
- License
- MIT
Diagnose "my CI failed on a file I didn't change — the test passes locally but CI insists there's a duplicate / conflict / lint violation that isn't in my branch." Caused by GitHub Actions checking out `refs/pull/N/merge` (the auto-computed merge of PR head + base) on `pull_request` events. Use when: (1) CI fails on a `git`/lint/whole-tree check (duplicate IDs, schema drift, file-content audit) that PASSES on the same SHA locally, (2) you're working in a dense parallel-PR window where main is…
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
# GHA `pull_request` Event Uses Merge-Ref, Not Head-Ref ## Problem You push a commit to a PR branch at T0. CI starts running at T0+10s. A sibling PR merges to main at T0+5s. Your CI run **sees the sibling's changes mixed into your branch** and fails on something neither side introduced alone. Most confusingly: locally on the exact same commit SHA, every check passes. `gh run view <N> --json headSha` reports your SHA correctly. `git show <SHA>:<file>` shows your file is clean. But CI failed on that SHA citing duplicates / conflicts / violations that aren't there. ## Context / Trigger Conditions - CI failure on a `pull_request` event (NOT `push`) - Failure cites a violation in a file you didn't touch in your last push - The same SHA passes the same check locally - `gh run view <N> --json headSha` matches your local HEAD - `git fetch origin main && git rev-list --left-right --count origin/main...HEAD` shows main is ahead by 1+ commits since your push - The failure message references identifiers / strings present in main but not in your branch (e.g. "duplicate ID `X`" where `X` was added to main by a PR that merged seconds before your CI ran) …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gha-pr-merge-ref-shows-upstream-changes@sha256:ae915941032c719dThe line at the top of this page pins the label v1.0.1, 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_cocmupez4y4rqr57)
3 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 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-08-12 | f461c97 | 9,509 B | A | view · diff |
| v1.0.1 | 2026-08-10 | ff2caaa | 9,102 B | A | view · diff |
| v1.0.0 | 2026-08-05 | e3930cf | 9,074 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 9,277 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 9,246 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 (9509 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_cocmupez4y4rqr57 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gha-pr-merge-ref-shows-upstream-changes GET https://markdownregistry.com/api/v1/blob/ae915941032c719dd56687c29728bdfec2c42919a7cb8e2dca1bc3ae15c1dc73
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.