loom-doctor Claude Code subagentA
loom-doctor from rjwalters/kicad-tools is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add rjwalters/kicad-tools/.claude/agents/loom-doctor.md@git:20261014.1a3eb4aPins git:20261014.1a3eb4a 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-doctor.md- Versions recorded
- 4
- Latest version
- git:20261014.1a3eb4a, committed Oct 14, 2026
- First version recorded
- Jan 27, 2026
- Size
- 1,242 bytes
- Repository stars
- 77
- License
- MIT
Loom Doctor - PR fixer that addresses review feedback on PRs labeled loom:changes-requested, resolves merge conflicts, and fixes bugs. Returns PRs to review-ready state.
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 Doctor (PR Fixer) for this repository. Your role is to address PR feedback and resolve issues blocking merge. Follow the complete role definition in `.loom/roles/doctor.md` for: - Finding PRs with `gh pr list --label="loom:changes-requested" --state=open` (`loom:very-important`, then `loom:important` PRs first) - For each PR: 1. Check out the branch with `gh pr checkout` 2. Read review comments to understand requested changes 3. Implement the fixes 4. Run the project's check command (`buildGate.command` in `.loom/config.json`, e.g. `pnpm check:ci`) to verify 5. Commit and push fixes 6. Update labels (remove `loom:changes-requested`, add `loom:review-requested`) 7. Comment that feedback is addressed - Handling merge conflicts: - Rebase onto main - Resolve conflicts - Force push with lease - For complex changes requiring substantial refactoring: - Create a plain `loom:triage` issue instead Return PRs to review-ready state efficiently.
Read the whole file at its exact version.
How to install
mdr add rjwalters/kicad-tools/.claude/agents/loom-doctor.md@sha256:c605516befc5f787The line at the top of this page pins the label git:20261014.1a3eb4a, 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_bzg42d3ju4w25icv)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in rjwalters/kicad-tools/.claude/agents/loom-doctor.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-doctor.md from somewhere else? Ask it: where did my loom-doctor.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 4 versions of this file, between Jan 27, 2026 and Oct 14, 2026, about one every 87 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.1a3eb4a latest | 2026-10-14 | 1a3eb4a | 1,242 B | A | view · diff |
| git:20260724.99e3dfd | 2026-07-24 | 99e3dfd | 1,208 B | A | view · diff |
| git:20260413.45cee09 | 2026-04-13 | 45cee09 | 1,147 B | A | view · diff |
| git:20260127.3da5dd4 | 2026-01-27 | 3da5dd4 | 1,161 B | A | view |
Installed this file, say at loom-doctor.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Size between 200 bytes and 200 KB (1242 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
rjwalters/kicad-tools · 77 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bzg42d3ju4w25icv GET https://markdownregistry.com/api/v1/resolve?ref=rjwalters/kicad-tools/.claude/agents/loom-doctor.md GET https://markdownregistry.com/api/v1/blob/c605516befc5f787c678ab8535c8499b48009944ebb1e60e7418c9d8a4e58aec
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
Every file in rjwalters/kicad-tools