merged-pr-not-deployed-gate-label-missing SKILL.md skillA
merged-pr-not-deployed-gate-label-missing 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/merged-pr-not-deployed-gate-label-missing@v1.2.1Pins v1.2.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/merged-pr-not-deployed-gate-label-missing/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.1, committed Aug 12, 2026
- First version recorded
- Jul 8, 2026
- Size
- 18,101 bytes
- Repository stars
- 3
- License
- MIT
Diagnose "I merged my PR + CI is green but the live service still doesn't show my changes." Use when: (1) a code-bearing PR has been squash-merged into main with all required status checks passing, (2) the user reports the change is still missing from the deployed environment minutes-to-hours later, (3) the repo has a `pull_request: types: [closed]` workflow gated on a label (typically `auto-deploy`, `deploy`, `ship-it`) and/or a path filter, (4) the deploy workflow's run row in `gh run list`…
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
# Merged PR Not Deployed — Gate Label / Path Filter Quietly Skipped the Workflow ## Problem A code change is merged into main and CI is green. The user opens the live service expecting to see the change and it's not there. The natural first instinct is "Cloud Run is caching" or "the bake hasn't re-run yet" or "I'm looking at the wrong revision". The actual cause is much simpler and quieter: **the deploy workflow never ran**, because the PR didn't satisfy the workflow's `if:` gate (typically a required label like `auto-deploy`, or a path filter that excludes the changed files). The trap is that GHA's `conclusion=skipped` looks visually identical to `conclusion=success` in the workflow run summary on the PR page and in `gh run list` — same green checkmark icon, same "completed" status. Nothing on the PR's "all checks passed" surface tells you the deploy didn't happen. This is a sister symptom to `gha-auto-deploy-never-ran-skipped-mask` (the FIRST-time-the-gate-fires-and-finds-an-infra-gap pattern), but a distinct cause: here the gate works as designed, the PR simply didn't carry the label. ## Context / Trigger Conditions All of these are typically true: …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/merged-pr-not-deployed-gate-label-missing@sha256:928662298a36da1bThe line at the top of this page pins the label v1.2.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_idjr3ufxeau3vqoj)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 8, 2026 and Aug 12, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.1 latest | 2026-08-12 | 9a8e5a8 | 18,101 B | A | view · diff |
| v1.2.1 | 2026-08-11 | f274e4b | 18,008 B | A | view · diff |
| v1.2.1 | 2026-08-06 | a81b2a1 | 18,011 B | A | view · diff |
| v1.2.0 | 2026-07-08 | b0f0d02 | 17,814 B | A | view · diff |
| v1.2.0 | 2026-07-08 | f1254dd | 17,842 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 (18101 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_idjr3ufxeau3vqoj GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/merged-pr-not-deployed-gate-label-missing GET https://markdownregistry.com/api/v1/blob/928662298a36da1bfa70633ff41c4c13a2964188fab7e3875e1cc6f7e3eb031c
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.