worktree-parallel SKILL.md skillA
worktree-parallel from d-robotics/moss is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add d-robotics/moss/worktree-parallel@git:20260930.19b5eadPins git:20260930.19b5ead in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- d-robotics/moss
- Path
.moss/skills/worktree-parallel/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.19b5ead, committed Sep 30, 2026
- Size
- 1,255 bytes
- Repository stars
- 143
- License
- MIT
How to run writable sub-agents in isolated git worktrees and merge their lease patches.
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
# Worktree-parallel writable sub-agents 1. In `fan_out_subagents`, give each implementation task `scope: "full"`, declared `writePaths`, and `worktree: true` (or set `MOSS_WORKTREE_SUBAGENTS=1` once and full-scope tasks default to isolated worktrees). 2. Each child then works in its own `git worktree` under `.moss/worktrees/` — concurrent writers cannot see or stomp each other. 3. On completion the child's changes are collected as a binary patch under `.moss/patches/<leaseId>.patch`; its summary ends with `[worktree lease=<id> patch=<digest> changed=<n>]`. 4. Merge leases back with `merge_subagent_patch` (leaseId + patchId from the child result). Merging uses `git apply --3way`, so changes in different regions of a file compose; a same-region collision returns `merge_conflict` with the conflicting paths — resolve manually, do not force. 5. Merge order matters when tasks touch the same files: merge one, verify, then the next. 6. Worktrees are cleaned up automatically after patch collection; the patch files remain for audit.
Read the whole file at its exact version.
How to install
mdr add d-robotics/moss/worktree-parallel@sha256:defaf7014d08a24eThe line at the top of this page pins the label git:20260930.19b5ead, 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_yb3t62zg3i6wcp6z)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 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 (1255 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
d-robotics/moss · 143 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yb3t62zg3i6wcp6z GET https://markdownregistry.com/api/v1/resolve?ref=d-robotics/moss/worktree-parallel GET https://markdownregistry.com/api/v1/blob/defaf7014d08a24e326b8e06bb864afc4c9fc4fe52c299f49f3cf02afc84228d
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.