worktree-write-abs-path-lands-in-parent-checkout SKILL.md skillA
worktree-write-abs-path-lands-in-parent-checkout 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/worktree-write-abs-path-lands-in-parent-checkout@v1.0.0Pins v1.0.0 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/worktree-write-abs-path-lands-in-parent-checkout/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Jul 8, 2026
- Size
- 4,934 bytes
- Repository stars
- 3
- License
- MIT
In a git worktree session, a Write/Edit whose absolute path points at the MAIN-REPO ROOT (the parent checkout) silently creates the file in that parent checkout's working tree — on whatever branch it has checked out — NOT in your worktree on your feature branch. The file then doesn't appear in `git status` on your branch and `ls`/Read inside the worktree can't find it. Use when: (1) the environment's "Primary working directory" is a worktree at `<repo>/.claude/worktrees/<name>/`, (2) you're…
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: Write to an absolute main-repo path lands in the parent checkout ## Problem You're working in a git worktree (`<repo>/.claude/worktrees/<name>/`) on a feature branch. You Write or Edit a file using an absolute path rooted at the repo's canonical location — `/Users/.../<repo>/docs/foo.md` — out of habit. The Write **succeeds**: that path is the *parent* checkout's working tree, which is a real, writable git working directory. So the file lands there, on whatever branch the parent checkout currently has (often a stale sibling worktree's branch), NOT in your worktree. Symptoms: the file you "just wrote" is absent from `git status` / `git add` on your branch; `ls`/Read inside the worktree reports "does not exist"; a commit silently omits the files. The write isn't lost — it's in the wrong tree. ## Context / Trigger Conditions - Environment's "Primary working directory" is `<repo>/.claude/worktrees/<name>/`. - You're Writing/Editing by ABSOLUTE path and typed the canonical repo root (no `.claude/worktrees/<name>/` segment). - Downstream signal: "file does not exist", unexpectedly clean `git status`, a …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/worktree-write-abs-path-lands-in-parent-checkout@sha256:ad63d4d223f3c61aThe line at the top of this page pins the label v1.0.0, 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_k7c537vof7qotpvo)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 8, 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 (4934 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_k7c537vof7qotpvo GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/worktree-write-abs-path-lands-in-parent-checkout GET https://markdownregistry.com/api/v1/blob/ad63d4d223f3c61a3a3f53d6feafbdbc498503c2a5238873f02a448bc65cdfc6
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.