gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row SKILL.md skillA
gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row 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/gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row@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/gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 17, 2026
- Size
- 7,180 bytes
- Repository stars
- 3
- License
- MIT
`gh pr checks` returns ONE exit status for the whole pull request, so a check your repo keeps red ON PURPOSE — a required aggregation context that is red while a PR is a draft, a placeholder context, a job the workflow allows to fail — makes the command exit non-zero on a pull request where everything that actually ran passed. Use when: (1) you are writing a background wait loop or watchdog that polls a PR and decides from `$?`; (2) a background poll came back "failed with exit code 1" and you…
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
# `gh pr checks` Folds a By-Design Red Into One Exit Status — Wait on the Row ## Problem You want a session to keep working while a pull request's cheap checks finish, so you background a poll and let the harness notify you when it exits. The obvious loop ends with `gh pr checks <n>` and trusts its exit status. On a pull request where **everything that ran passed**, that loop reports failure — because one context is red on purpose and the exit status has no room to say so. The notification reads `failed with exit code 1`, which is indistinguishable from the run genuinely going red, so the next thing the session does is diagnose a defect that does not exist, or hold a landing queue on a branch that is fine. ## Context / Trigger Conditions - You are writing a wait loop, watchdog, or `until`-style poll around a pull request. - A repo keeps a **required aggregation context red while the PR is a draft**, so that a draft cannot merge on a green produced by jobs that never ran. (This is a real and good pattern: the aggregate job prints a line in its own log saying it is red because the PR is a draft and no test suite has run on the code.) …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row@sha256:0d0498ee4ad76ff6The 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_rtd5tyr2zzqg6lwx)
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 (7180 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_rtd5tyr2zzqg6lwx GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gh-pr-checks-exit-code-folds-a-by-design-red-wait-on-the-row GET https://markdownregistry.com/api/v1/blob/0d0498ee4ad76ff6c5e5111a19d9faa4df16f86fb17765db9bf156140cf09349
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.