subagent-bash-cd-wrong-worktree SKILL.md skillA
subagent-bash-cd-wrong-worktree 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/subagent-bash-cd-wrong-worktree@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/subagent-bash-cd-wrong-worktree/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Jul 8, 2026
- First version recorded
- May 13, 2026
- Size
- 7,516 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and prevent subagents committing to the wrong git branch when dispatched in multi-worktree setups. Use when (1) you dispatched a subagent (Task tool) with bash steps like `cd <target-worktree> && git commit ...`, (2) the subagent reported DONE with a real-looking commit SHA, (3) `git log` on the target worktree doesn't show that SHA — but `git branch --contains <sha>` finds it on a sibling branch (typically the parent repo's checked-out branch). Root cause: each Bash tool call starts…
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
# Subagent + bash `cd` + multi-worktree → commit lands on wrong branch ## Problem You dispatched a subagent (via the Task tool) to do work in a specific git worktree. You wrote bash steps like: ```bash cd /path/to/.claude/worktrees/feature-X pip install -r requirements.txt git add foo.py git commit -m "..." ``` The subagent reports DONE with a commit SHA. The SHA is real (`git rev-parse <sha>` resolves) but `git log` on `feature-X`'s branch does not show it. `git branch --contains <sha>` reveals the commit landed on whatever branch was checked out in the **parent repository directory** (not your target worktree). **Why subagents miss this:** they trust their own `cd` step to have worked, then call `git commit` and see a successful commit message echoed by Git. Git commits the staged change to whatever HEAD is in the cwd Git resolves, which (after the shell reset) is the launch directory's HEAD — not the worktree's. ## Trigger Conditions - Multi-worktree git setup (`git worktree list` shows ≥ 2 entries) - Subagent dispatch (general-purpose Task tool, any model) - Subagent prompt instructed `cd <abspath> && <commands>` for shell steps …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/subagent-bash-cd-wrong-worktree@sha256:f101b637d62c7d6aThe 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_74qu5d6vmepmrlri)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 13, 2026 and Jul 8, 2026, about one every 56 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-07-08 | f1254dd | 7,516 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 7,173 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 (7516 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_74qu5d6vmepmrlri GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/subagent-bash-cd-wrong-worktree GET https://markdownregistry.com/api/v1/blob/f101b637d62c7d6aa31b8479f9f6d09ad46c12768be69f5c7fb4227fbea2cf55
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.