pr-monitor skillA
pr-monitor is agent-read markdown (skill) from ronaknnathani/relay: Handle one pull request attention event end to end — read the watcher digest, triage it, delegate the fixing to pr-fix, re-observe the pull request, and exit. Use when the PR watcher wakes you, or run it manually for a one-shot check of an open PR..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# PR Monitor Handle **one** pull request attention event, then stop. You are a **router**: the `relay pr watch` runtime does the observing, you interpret its digest, delegate the fixing to `pr-fix`, re-observe the pull request, and exit. You never write code, never post in your own voice, never approve, and never merge. There is **no acknowledgement**. The watcher never records that attention was handled, because a local claim can be wrong. Every tick re-reads the live pull request, and an item disappears only when the remote state itself no longer shows it: the check passes or reruns, the head SHA changes, the conflict clears, the thread resolves, your reply lands on that exact source, auto-merge is armed, or the pull request closes or merges. If nothing changed, the problem is still there and it will wake you again — which is correct. This skill has **no loop**. It does not schedule, does not recur, and does not own a next-tick time. The watcher owns cadence; one run of this skill owns one digest. ## Where the work comes from **Woken by the watcher.** The prompt names the project and a fingerprint: …
Read the whole file at its exact version.
How to install
mdr add ronaknnathani/relay/pr-monitor@git:20260902.6e57c00mdr add ronaknnathani/relay/pr-monitor@sha256:15b41d8697704f11Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_wziahud2ggim4gr2)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260902.6e57c00 latest | 2026-09-02 | 6e57c00 | 10,792 B | A | view · diff |
| git:20260629.91c930b | 2026-06-29 | 91c930b | 7,207 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 (10792 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
ronaknnathani/relay · 3 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wziahud2ggim4gr2 GET https://markdownregistry.com/api/v1/resolve?ref=ronaknnathani/relay/pr-monitor GET https://markdownregistry.com/api/v1/blob/15b41d8697704f1190d5df699dd06c6888e058cf9b82131144bc6f862d3b38ea
Your agent 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.