loom-judge Claude Code subagentA

loom-judge from rjwalters/kicad-tools is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.

Install it, pinned
mdr add rjwalters/kicad-tools/.claude/agents/loom-judge.md@git:20261019.975de65

Pins git:20261019.975de65 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
Claude Code subagent
Repository
rjwalters/kicad-tools
Path
.claude/agents/loom-judge.md
Versions recorded
5
Latest version
git:20261019.975de65, committed Oct 19, 2026
First version recorded
Feb 27, 2026
Size
1,448 bytes
Repository stars
77
License
MIT

Loom Judge - Code review specialist that reviews PRs labeled loom:review-requested. Use when reviewing pull requests for code quality, security, and best practices.

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

You are the Loom Judge (Code Review Specialist) for this repository.

Your role is to review PRs labeled `loom:review-requested` with thoroughness and expertise.

Follow the complete role definition in `.loom/roles/judge.md` for:
- Finding PRs with `gh pr list --label="loom:review-requested"` (`loom:very-important`, then `loom:important` PRs first; same bar)
- Checkout and review process
- Running the project's check command (`buildGate.command` in `.loom/config.json`, e.g. `pnpm check:ci`) for CI validation
- **Verifying CI passes** with `loom-daemon forge wait-checks` before approval (REQUIRED)
- **Checking merge state** with `gh pr view --json mergeStateStatus` (must be CLEAN)
- Code quality and security assessment
- Approval workflow: `gh pr comment` with feedback, then update labels (remove `loom:review-requested`, add `loom:pr`)
- Change request workflow: `gh pr comment` with feedback, then update labels (remove `loom:review-requested`, add `loom:changes-requested`)
- Providing specific, actionable feedback
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add rjwalters/kicad-tools/.claude/agents/loom-judge.md@sha256:58e9fa90e94e6871

The line at the top of this page pins the label git:20261019.975de65, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ywr5qdkedqbuylqx.svg)](https://markdownregistry.com/a/art_ywr5qdkedqbuylqx)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in rjwalters/kicad-tools/.claude/agents/loom-judge.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of loom-judge.md from somewhere else? Ask it: where did my loom-judge.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Feb 27, 2026 and Oct 19, 2026, about one every 59 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261019.975de65 latest2026-10-19 975de65 1,448 BA view · diff
git:20261014.1a3eb4a2026-10-14 1a3eb4a 1,436 BA view · diff
git:20260724.99e3dfd2026-07-24 99e3dfd 1,364 BA view · diff
git:20260413.45cee092026-04-13 45cee09 1,298 BA view · diff
git:20260227.379d1252026-02-27 379d125 1,310 BA view
Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (1448 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

GitHub

rjwalters/kicad-tools · 77 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ywr5qdkedqbuylqx
GET https://markdownregistry.com/api/v1/resolve?ref=rjwalters/kicad-tools/.claude/agents/loom-judge.md
GET https://markdownregistry.com/api/v1/blob/58e9fa90e94e687157b5369bfc5b2549df7010b7e2315701def25d7451fcf7cd

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: which agent file does what.

More from rjwalters/kicad-tools

loom-architect SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-architect/SKILL.md · Identifies improvement opportunities and creates proposals
git:20261014.c9e8426 · audit A · 77 stars
loom-auditor SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-auditor/SKILL.md · Verifies claims made by other agents against runtime reality by building and testing software
git:20261014.c9e8426 · audit A · 77 stars
loom-builder-complexity SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-builder-complexity/SKILL.md · This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the…
git:20261014.394e76a · audit A · 77 stars
loom-builder-pr SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-builder-pr/SKILL.md · This document covers PR creation, test output handling, and quality requirements for the Builder role. For the core…
git:20261026.79cebff · audit A · 77 stars
loom-builder-worktree SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-builder-worktree/SKILL.md · This document covers git worktree management for the Builder role. For the core builder workflow, see `builder.md`.
git:20261014.c9e8426 · audit A · 77 stars
loom-builder SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-builder/SKILL.md · Implements issues labeled loom:issue (human-approved work)
git:20261117.d2f58d4 · audit B · 77 stars
loom-cargo-target-isolation SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-cargo-target-isolation/SKILL.md · **Load when**: you are about to run (or just ran) a local `cargo build`/`cargo test`/`cargo run` whose result will…
git:20261012.bf4491e · audit A · 77 stars
loom-champion SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-champion/SKILL.md · Human avatar for final decisions - promotes quality issues to approved status AND auto-merges Judge-approved PRs that…
git:20261101.cb06282 · audit A · 77 stars
loom-ci-refusals-reference SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-ci-refusals-reference/SKILL.md · **Load when**: `loom-daemon forge wait-checks` printed `LOOM-CHECKS-ERROR` naming an HTTP `401`/`403`/`429`, it left a…
git:20261007.6b901b8 · audit A · 77 stars
loom-comment-body-literal-path SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-comment-body-literal-path/SKILL.md · Single canonical copy; role prompts' short pointers refer here.
git:20261010.688914e · audit A · 77 stars
loom-curator-estimate SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-curator-estimate/SKILL.md · For every issue you actually curate or re-curate, write exactly one concrete, standalone comment in the current issue…
git:20261016.bd59834 · audit A · 77 stars
loom-curator-rate-budget SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-curator-rate-budget/SKILL.md · Why `curator.md`'s per-issue recipes are REST, and what is still unmeasured.
git:20261005.f192e8f · audit A · 77 stars

Every file in rjwalters/kicad-tools

Other files named loom-judge

loom-judge SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-judge/SKILL.md · Reviews PRs labeled loom:review-requested
git:20261117.d2f58d4 · audit B · 77 stars
loom-judge SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-judge/SKILL.md · Reviews PRs labeled loom:review-requested
git:20261117.d2f58d4 · audit B · 77 stars

Browse by kind, by grade A, or by owner.