reviewer-runner SKILL.md skillA
reviewer-runner from zhiming-dev/roster is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zhiming-dev/roster/reviewer-runner@git:20260607.31b1c63Pins git:20260607.31b1c63 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zhiming-dev/roster
- Path
reviewer-agent/reviewer-runner/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260607.31b1c63, committed Jun 7, 2026
- Size
- 2,491 bytes
- Repository stars
- 12
- License
- MIT
Review a diff against a task's success criteria. Use when: a `task_assignment` for role `reviewer` lands; you need to lint, summarize a diff, or produce structured review comments.
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
# Reviewer Runner
## When to Use
- The Planner dispatches a `task_assignment` for role `reviewer`.
- An upstream task has produced a diff artifact and a `successCriteria` to review against.
## Prerequisites
- Read [`reviewer.agent.md`](../reviewer.agent.md).
- Read [`shared/approval-gate/SKILL.md`](../../shared/approval-gate/SKILL.md) and
[`shared/provenance/SKILL.md`](../../shared/provenance/SKILL.md).
## Procedure
1. **Read the task + upstream diff.** Confirm `assigneeRole === "reviewer"` and the
`inputs.diffPath` points at an existing artifact.
2. **Emit `task_started`.**
3. **Run linters** appropriate for the changed files (`eslint`, `ruff`, `golangci-lint`, etc.).
Capture output under `runs/<runId>/artifacts/<task-id>/lint.log`.
4. **Read the diff** and judge each hunk against the upstream task's `successCriteria`.
5. **Write the review** at `runs/<runId>/artifacts/<task-id>/review.md` with two sections:
- **Blocking** — criterion violations, correctness bugs, security issues, missing tests
for a behavior change. Each item cites `file:line` and the criterion it violates.
- **Non-blocking** — style, naming, suggestions. Do **not** gate on these.
…Read the whole file at its exact version.
How to install
mdr add zhiming-dev/roster/reviewer-runner@sha256:b4dae2a5acb6665bThe line at the top of this page pins the label git:20260607.31b1c63, 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_anp6tsv6mt5drtf6)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 7, 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 (2491 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
zhiming-dev/roster · 12 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_anp6tsv6mt5drtf6 GET https://markdownregistry.com/api/v1/resolve?ref=zhiming-dev/roster/reviewer-runner GET https://markdownregistry.com/api/v1/blob/b4dae2a5acb6665bd1decb32a69b78459a09cfadea0bcbeae7944f459dbefa40
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.