gh-pr-merge-worktree-checkout-trap SKILL.md skillA
gh-pr-merge-worktree-checkout-trap 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/gh-pr-merge-worktree-checkout-trap@v1.5.0Pins v1.5.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/gh-pr-merge-worktree-checkout-trap/SKILL.md- Versions recorded
- 4
- Latest version
- v1.5.0, committed Jul 10, 2026
- First version recorded
- May 13, 2026
- Size
- 14,141 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and bypass `gh pr merge --squash --delete-branch` failing with "failed to run git: fatal: 'main' is already used by worktree at ..." when another git worktree has main checked out. Use when: (1) you run gh pr merge and see this exact error, (2) you have multiple worktrees in the repo (e.g. `.claude/worktrees/*`), (3) the error appears even though the GitHub merge itself looks fine. The merge SUCCEEDED on GitHub — only gh's local-side effect (post-merge `git checkout main`) failed.…
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
# `gh pr merge` Worktree-on-Main Checkout Trap ## Problem `gh pr merge --squash --delete-branch` (and similar commands) fail with: ``` failed to run git: fatal: 'main' is already used by worktree at '/path/to/another/worktree' ``` even when the user has every right to merge the PR. The error makes it look like the merge failed, prompting the user to retry or panic. **The merge actually succeeded on GitHub.** Only `gh`'s post-merge local side-effect — switching the local working tree to `main` so it's "ready" after the merge — failed because git refuses to check out a branch that's already checked out in another worktree. ## Context / Trigger Conditions You are in the right place if **all** of these are true: - You ran `gh pr merge <number>` (any merge mode: `--squash` / `--merge` / `--rebase`). - The exact error includes `fatal: 'main' is already used by worktree at`. - The repo has multiple `git worktree` entries (run `git worktree list` to confirm). - One of those worktrees is on `main` (or whichever branch the PR merged into). The command's first action is the GitHub merge API call; the local checkout …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gh-pr-merge-worktree-checkout-trap@sha256:e11bdf74a30484b1The line at the top of this page pins the label v1.5.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_rsrpivv7fj2sjl2b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Jul 10, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.5.0 latest | 2026-07-10 | 7b8aaba | 14,141 B | A | view · diff |
| v1.4.0 | 2026-07-08 | f1254dd | 13,060 B | A | view · diff |
| v1.3.0 | 2026-05-29 | 059688a | 11,511 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 6,655 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 (14141 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_rsrpivv7fj2sjl2b GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gh-pr-merge-worktree-checkout-trap GET https://markdownregistry.com/api/v1/blob/e11bdf74a30484b18de018547840862fb9f290f424e74d6c31a7ad930a1ccce7
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.