gh-pr-create-orchestration-cwd-wrong-head SKILL.md skillA
gh-pr-create-orchestration-cwd-wrong-head 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-create-orchestration-cwd-wrong-head@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/gh-pr-create-orchestration-cwd-wrong-head/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- May 29, 2026
- Size
- 6,245 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and prevent `gh pr create` opening a PR against the WRONG head branch when invoked from a parallel-orchestration setup with multiple worktrees. Use when: (1) you've dispatched subagents to work in sub-worktrees but you're finalizing PRs from a separate orchestration worktree, (2) `gh pr create` succeeds but `gh pr view --json headRefName` shows your orchestration worktree's branch (e.g. `docs/sNNN-handoff`) instead of the feature branch the subagent committed to (e.g. `fix/issue-X`)…
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 create` from orchestration worktree picks wrong head branch ## Problem In a parallel-execution setup, an orchestrator dispatches sub-agents to feature worktrees (`<repo>/.claude/worktrees/feature-A/`, `feature-B/`, etc.) and waits on their completion. When the orchestrator then runs `gh pr create` to open the PR for one of those features, **it gets opened against whatever branch is currently checked out in the orchestrator's CWD** — not the feature branch the subagent committed to. Result: a PR with the right title and body but the wrong head branch (typically the orchestrator's `docs/sNNN-handoff` or `main`-tracking branch). The PR's diff is unrelated to the change description, and the actual feature work never gets a PR. ## Trigger conditions You're hitting this skill if **all** of: 1. Your workflow has multiple worktrees: one orchestrator + N feature worktrees. 2. You ran `gh pr create` (with title + body via heredoc) from the orchestrator's working directory. 3. `gh pr view <N> --json headRefName` returns your orchestrator's branch (e.g. `docs/sNNN-handoff`), NOT the feature branch (e.g. `fix/issue-XXX`). …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gh-pr-create-orchestration-cwd-wrong-head@sha256:e9f6a50c66b4cd40The 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_xx24jrthdf2htelr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 29, 2026 and Aug 11, 2026, about one every 37 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 6,245 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 6,271 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 6,240 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 (6245 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_xx24jrthdf2htelr GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gh-pr-create-orchestration-cwd-wrong-head GET https://markdownregistry.com/api/v1/blob/e9f6a50c66b4cd40148986ff07a6df4d38c6829e70c3675d34134a0e44bd66a1
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.