pr-hijack-via-stale-worktree-branch-ref SKILL.md skillA
pr-hijack-via-stale-worktree-branch-ref 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/pr-hijack-via-stale-worktree-branch-ref@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/pr-hijack-via-stale-worktree-branch-ref/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Aug 12, 2026
- First version recorded
- May 13, 2026
- Size
- 10,375 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and recover from accidentally overwriting another session's open PR when `git push -u origin <branch>` in a long-lived worktree silently replaces the remote branch ref. Use when ANY of the following appears: (1) you ran `git checkout -b <branch> origin/main` and `git push -u` and git reported `* [new branch]` even though the branch already existed upstream, (2) `gh pr create` then errors with `a pull request for branch "<branch>" into branch "main" already exists` pointing to a PR you…
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
# PR-Hijack via Stale Worktree Branch Ref ## Problem In a long-lived git worktree (especially `.claude/worktrees/<name>/` patterns created by a parallel-session harness), a same-named local branch can be created via `git checkout -b X origin/main` even when branch `X` already exists upstream with an open PR. Pushing that local branch with `git push -u origin X` succeeds — git reports `* [new branch]` — and silently replaces the remote ref. The result: - The remote branch ref now points at YOUR commit - The open PR (call it #N) on that branch now lists YOUR commit - PR #N's title and body still describe the ORIGINAL author's work - The original author's commit is orphaned on the remote but still reachable in YOUR local reflog (because the worktree's reflog captured it earlier) - `gh pr create` fails with `a pull request for branch "X" into "main" already exists` and surfaces PR #N — which is now an artefact of two unrelated commits The hijack is silent on both sides: git's push output doesn't warn, gh doesn't either, and the PR's web view shows a perfectly plausible (but wrong) state. ## Context / Trigger Conditions Surfaces when ALL of: …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/pr-hijack-via-stale-worktree-branch-ref@sha256:4c12739ca0e00a32The 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_a6itakd7cmackgxn)
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 Aug 12, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-12 | f461c97 | 10,375 B | A | view · diff |
| v1.0.0 | 2026-08-05 | e3930cf | 10,370 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 10,597 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 10,566 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 (10375 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_a6itakd7cmackgxn GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/pr-hijack-via-stale-worktree-branch-ref GET https://markdownregistry.com/api/v1/blob/4c12739ca0e00a32449827e6ea08d824442e3405f696e6252e1866b776b85045
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.