subagent-driven-branch-ref-froze-stranded-commits SKILL.md skillA
subagent-driven-branch-ref-froze-stranded-commits 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-driven-branch-ref-froze-stranded-commits@v1.0.1Pins v1.0.1 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-driven-branch-ref-froze-stranded-commits/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.1, committed Sep 12, 2026
- First version recorded
- May 29, 2026
- Size
- 12,990 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and recover from "PR merged, but half my work is missing from main" cases in `superpowers:subagent-driven-development` (or similar one-fresh-subagent-per-task) sessions, where committed work survives in the worktree's `HEAD` chain but never makes it into the pushed branch ref. Use when ANY of these appears: (1) `gh pr view <N>` body claims "M files changed, N insertions" but `gh pr diff <N> --name-only | wc -l` returns a smaller number than you expect…
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-driven session left commits stranded — branch ref froze while worktree HEAD advanced ## Problem You ran a long `superpowers:subagent-driven-development` (or similar fresh- subagent-per-task) session in a worktree. Each subagent did its task, committed its work, the controlling session ran spec + code-quality review per task, all green. At the end you pushed the worktree's branch to origin, opened a PR, CI went green, you squash-merged. Hours or one session later, somebody runs `pytest` on freshly-pulled main and gets a `ModuleNotFoundError`, a missing-file assertion, or a `sql_path missing` error pointing at code that **was definitely committed** during the session. `git log` in your old worktree still shows all the commits at the top of the branch. But on main, half of them are gone. The squash commit on main contains only the early portion of your work — typically the first N tasks before some specific transition point. Tasks after that point exist as commits in the worktree (`git log` shows them) but did not reach origin, did not reach the PR, did not reach the merge. ## Context / Trigger Conditions Strong signal **after** the merge: …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/subagent-driven-branch-ref-froze-stranded-commits@sha256:28e4a069982c0952The line at the top of this page pins the label v1.0.1, 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_mavfjbiuy35nlzio)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 29, 2026 and Sep 12, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-09-12 | aec1aa9 | 12,990 B | A | view · diff |
| v1.0.1 | 2026-08-05 | ef4b211 | 14,042 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 14,043 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 14,012 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 (12990 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_mavfjbiuy35nlzio GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/subagent-driven-branch-ref-froze-stranded-commits GET https://markdownregistry.com/api/v1/blob/28e4a069982c09523432d5f712e2c3a74a44ab8c44744da8dabd09865c87e27c
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.