cross-worktree-spec-handoff-via-checkout-paths SKILL.md skillA
cross-worktree-spec-handoff-via-checkout-paths from wan-huiyan/agent-traffic-control is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wan-huiyan/agent-traffic-control/cross-worktree-spec-handoff-via-checkout-paths@v1.3.1Pins v1.3.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wan-huiyan/agent-traffic-control
- Path
plugins/agent-traffic-control/skills/cross-worktree-spec-handoff-via-checkout-paths/SKILL.md- Versions recorded
- 6
- Latest version
- v1.3.1, committed Sep 22, 2026
- First version recorded
- Jul 8, 2026
- Size
- 15,530 bytes
- Repository stars
- 3
- License
- MIT
Pass a shared file between two parallel sessions in different worktrees or branches, without merging to main first — a design spec, docs, a handoff prompt, a mockup. `git checkout <branch> -- <paths>` stages it. Use when a session says "the file doesn't exist". Not co editing.
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
# Cross-worktree spec handoff via `git checkout <branch> -- <paths>` ## Problem You ran a brainstorming / design session in Claude Code session A. Output: design spec doc, a handoff prompt, a vibe mockup HTML. You committed them on branch `worktree-spec-A` in `.claude/worktrees/spec-A/`. You then started Claude Code session B in a different worktree, on a fresh branch `feat/something-B` branched from `main`. Session B is supposed to consume the design spec — but the spec doc, handoff prompt, and mockup files **don't exist** in B's working tree, because B's branch was cut from main before A's commits landed and the commits never made it to main. Session B reports: "the referenced design spec files don't exist in the handover. Let me look at what's available." → it's blocked. The naive fix is "merge A's branch into main, then B pulls main". That needs a PR review cycle. Slow. ## Context / Trigger Conditions All of: - Two (or more) Claude Code sessions are running in parallel, in **different worktrees** of the same repo. (`git worktree list` shows multiple paths.) - Session A (the producer) committed artefacts — design docs, plans, spec …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/cross-worktree-spec-handoff-via-checkout-paths@sha256:bd1265387f25327eThe line at the top of this page pins the label v1.3.1, 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_xkqq2iqj4r3yezhk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 8, 2026 and Sep 22, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.1 latest | 2026-09-22 | 05de8be | 15,530 B | A | view · diff |
| v1.3.1 | 2026-08-10 | 5b6d8a2 | 15,110 B | A | view · diff |
| v1.3.1 | 2026-08-10 | a58c34c | 15,090 B | A | view · diff |
| v1.3.1 | 2026-08-10 | a39e221 | 16,345 B | A | view · diff |
| v1.3.1 | 2026-08-05 | ef4b211 | 15,448 B | A | view · diff |
| v1.3.0 | 2026-07-08 | f1254dd | 16,123 B | A | view |
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 (15530 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
wan-huiyan/agent-traffic-control · 3 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xkqq2iqj4r3yezhk GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/cross-worktree-spec-handoff-via-checkout-paths GET https://markdownregistry.com/api/v1/blob/bd1265387f25327ea647bad0fe6b8f6b4dd3c5f8ba35fa1e30fa56b5e8b4d529
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.