remote skillB
remote is agent-read markdown (skill) from jebel-quant/rhiza-claude: Check what CI on the origin says about this repo's open pull/merge requests, then diagnose and fix the red ones on their own branches. Reads the forge, reproduces locally, pushes fixes to the request's branch — never to the default branch..
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
You are running `/remote` in the **current working directory's repo**. **The gap this closes.** `/rhiza:quality` files findings as issues, those issues become branches, and the branches become requests that were green when they left. Local green and origin green are different claims, and only the second one merges. A suite that passes on a warm cache with the author's toolchain says nothing about a matrix leg on another OS, a lockfile the runner resolves differently, a gate that exists only in the workflow, or a network call that is rate-limited today. This command asks the forge what actually happened, and then fixes what it finds. It is the only rhiza command that reads CI. **One rule outranks everything below: never make a check green by weakening it.** Deleting the failing test, lowering the threshold, narrowing the matrix, adding `continue-on-error` or `--ignore` — each of those turns a red build into a green one without changing what is broken, and the next person inherits both the defect and a gate that will never mention it again. If the honest fix is out of reach, say so, leave the build red, and report why. A red request is information; a falsely green one is not. …
Read the whole file at its exact version.
How to install
mdr add jebel-quant/rhiza-claude/remote@git:20260822.f1c4320mdr add jebel-quant/rhiza-claude/remote@sha256:24ee4fc490f5aba1Pin 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_c6rsrlmmmcgzkttj)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260822.f1c4320 latest | 2026-08-22 | f1c4320 | 10,257 B | B | view · diff |
| git:20260815.806be7e | 2026-08-15 | 806be7e | 9,499 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10257 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
jebel-quant/rhiza-claude · 4 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c6rsrlmmmcgzkttj GET https://markdownregistry.com/api/v1/resolve?ref=jebel-quant/rhiza-claude/remote GET https://markdownregistry.com/api/v1/blob/24ee4fc490f5aba155aeafcbcf943e40514a44b7ad8a53ea6a23f2730b312c14
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.
More from jebel-quant/rhiza-claude
Every file in jebel-quant/rhiza-claude