pr-followup-commit-stranded-after-squash SKILL.md skillA
pr-followup-commit-stranded-after-squash 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-followup-commit-stranded-after-squash@v1.1.0Pins v1.1.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-followup-commit-stranded-after-squash/SKILL.md- Versions recorded
- 3
- Latest version
- v1.1.0, committed Jul 8, 2026
- First version recorded
- May 13, 2026
- Size
- 9,054 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and recover follow-up commits that were pushed to an open PR's branch but never reached `main` because the user squash-merged the PR between pushes. Use when: (1) you pushed commit 1, opened a PR, then iteratively pushed commits 2, 3, ... in response to user feedback, (2) you go to merge / verify and find the PR is already MERGED, (3) the squash commit on main has insertion counts / file content matching ONLY commit 1 — your follow-up commits are stranded on the now-closed branch.…
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
# Follow-up commits stranded after PR squash-merge ## Problem You've been iterating on a PR: pushed commit 1, opened the PR, then pushed commits 2 / 3 / ... in response to user feedback or new information. At some point the user merges the PR — possibly during one of your iterations, possibly before you finished pushing. The squash on `main` only contains commit 1's content. Your follow-up commits sit on the closed branch, never reaching `main`. If you ask `gh pr view N --json state` you see `MERGED`, but the merged content is missing your iterations. This is a silent failure. Nothing errors. The PR appears successfully shipped. But main is incomplete. ## Context / Trigger Conditions All of: 1. You pushed multiple commits asynchronously to a single PR's branch (not all at once before opening the PR). 2. You believed those commits would all land in the squash because they were on the branch at merge time. 3. `gh pr view N --json state` returns `MERGED`. 4. `git show <merge-commit> --stat` shows insertion counts matching only your *first* (or first few) commits — not all of them. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/pr-followup-commit-stranded-after-squash@sha256:64c528d8a7bfb0cfThe line at the top of this page pins the label v1.1.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_p6hx6x5pgk5rlhtb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 13, 2026 and Jul 8, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.0 latest | 2026-07-08 | f1254dd | 9,054 B | A | view · diff |
| v1.1.0 | 2026-05-29 | 059688a | 9,023 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 6,999 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 (9054 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_p6hx6x5pgk5rlhtb GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/pr-followup-commit-stranded-after-squash GET https://markdownregistry.com/api/v1/blob/64c528d8a7bfb0cf3c3e8844dfbaefa47787ac8a130f3af10a631aab6c250809
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.