batch-merge-subject-is-not-evidence-a-member-landed SKILL.md skillA
batch-merge-subject-is-not-evidence-a-member-landed 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/batch-merge-subject-is-not-evidence-a-member-landed@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/batch-merge-subject-is-not-evidence-a-member-landed/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 11, 2026
- Size
- 10,975 bytes
- Repository stars
- 3
- License
- MIT
You are about to close, delete the branch of, or mark as landed a pull request because a batch, roll-up or merge-train commit on the target branch names it in the subject line, and because the member's own commits all predate that merge by wall clock. Neither of those is evidence. A batch branch is assembled at some moment BEFORE it merges, so anything the member pushed after assembly is outside it, and the subject records INTENT at assembly time rather than CONTENT at merge time. Use before…
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
# A Batch's Subject Naming a Member Is Not Evidence the Member Landed ## Problem Several small pull requests were combined into one branch and landed together to save CI runs. The squash commit on the target branch says, in `git log`: ``` Batch: four small pull requests in one run — #2767, #2743, #2739, #2772 ``` That subject is written by the batch itself, it is in the permanent history, and it reads as a receipt. The obvious next step is to close each named member as already landed and delete its branch. **The subject is a claim about what was ASSEMBLED, not about what MERGED.** A batch branch is built at some moment T by merging or cherry-picking each member's head as it stood at T. The batch then sits in review, gates run, and it merges at some later moment. Everything a member pushed between T and the merge is outside the batch and is not on the target branch, while the subject still names that member exactly as before. Nothing in the batch notices. The member's branch is not rewritten, no conflict is raised, no gate fails, and the batch's own diff looks complete because it IS complete with respect to the heads it was built from. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/batch-merge-subject-is-not-evidence-a-member-landed@sha256:d05955d1a5625a0bThe 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_mygpigpwzm4hovip)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 11, 2026.
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 (10975 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_mygpigpwzm4hovip GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/batch-merge-subject-is-not-evidence-a-member-landed GET https://markdownregistry.com/api/v1/blob/d05955d1a5625a0b41a6f2164ff1db70fa14fa64f3eb5e93a0c8c737d470b938
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.