conflicted-pr-starts-no-ci-run-push-resolution-first SKILL.md skillA
conflicted-pr-starts-no-ci-run-push-resolution-first 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/conflicted-pr-starts-no-ci-run-push-resolution-first@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/conflicted-pr-starts-no-ci-run-push-resolution-first/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 17, 2026
- Size
- 13,042 bytes
- Repository stars
- 3
- License
- MIT
A conflicted pull request stops producing NEW CI runs for as long as the conflict stands, because the provider rebuilds the synthetic merge ref whenever either side moves and cannot build it for a conflicting PR. The run list is usually NOT empty: it still holds the head's PRE-conflict run, and that run's red is then read as the blocker. Use when: (1) a landing script refuses to step a PR and prints something like `DRAFT UNKNOWN (git: CONFLICTED vs origin/main <sha>) gates=failure…
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
# A Conflicted PR Starts No CI Run — Push the Resolution First ## Problem Your pull request is conflicted. Someone — a coordinator, a landing script, or you — reads its status and sees three fields: ``` #1234 DRAFT UNKNOWN (git: CONFLICTED vs origin/main abc1234de) gates=failure auto-merge=NOT armed ``` **Two of those three are non-facts.** The required check is red because the PR is a draft (in repos where a draft's required context is deliberately red) or because the newest run on that SHA is a *stale* one that died — either way it is not the blocker. `UNKNOWN` is not "not conflicted": the provider invalidates mergeability for every open PR each time the base moves and returns `UNKNOWN` until it recomputes, which is the usual cause on a busy base. The only fact in the line is the parenthesis, which came from `git merge-tree`. The expensive half is what is *missing*: **no NEW run is created for as long as the conflict stands.** A `pull_request` workflow runs against the synthetic merge ref, and the provider rebuilds that ref whenever either side moves — so when the two genuinely conflict there is nothing to check out and no run is …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/conflicted-pr-starts-no-ci-run-push-resolution-first@sha256:415b67745c7359faThe 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_vnsicawgkvc3rgqk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 17, 2026.
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 (13042 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_vnsicawgkvc3rgqk GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/conflicted-pr-starts-no-ci-run-push-resolution-first GET https://markdownregistry.com/api/v1/blob/415b67745c7359fa1d380df41aebc7706ff90e8abaef8dce4e8b1097e6229471
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.