clean-merge-lands-line-guard-on-a-value-neither-branch-predicted SKILL.md skillA
clean-merge-lands-line-guard-on-a-value-neither-branch-predicted 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/clean-merge-lands-line-guard-on-a-value-neither-branch-predicted@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/clean-merge-lands-line-guard-on-a-value-neither-branch-predicted/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Sep 17, 2026
- Size
- 8,781 bytes
- Repository stars
- 3
- License
- MIT
Two branches each contain a guard, test or document that pins a line NUMBER in a third file, each side correctly re-aims that number for its own tree, and git merges both edits with NO conflict — leaving a merged tree whose real line can be neither number. Use when: (1) two parallel PRs both insert or delete lines in a file that other files cite by line, (2) a merge you just completed touched a test or page that resolves `path:NNN` and the merge was clean, (3) a guard file in your merge result…
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 Clean Merge Lands a Line Guard on a Value Neither Branch Predicted ## Problem A repo has guards that pin line numbers: a test asserting that `handler.py:992` still reads `if name not in REGISTRY:`, a published page citing `handler.py:1559`, a docstring citing `handler.py:1582` for the line its own example came from. They exist because the statement is stable and its address is not. Two branches are open. Branch A inserts 22 lines into `handler.py` and, being careful, re-aims the three citations that moved — for **its** tree. Branch B adds 64 lines to a different file and re-aims the same two guard files — for **its** tree. Each side is right. The edits are in different lines of the same files, so git merges them **cleanly**. The merged tree is the first tree either set of numbers has ever been read against, and it can agree with neither. Nothing conflicts, no gate is red at merge time, and the guard fails later — on the base branch, and then on every branch queued behind it. **The trap is psychological rather than technical.** After the merge, those guard files look freshly fixed: modified minutes ago, by a competent session, …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/clean-merge-lands-line-guard-on-a-value-neither-branch-predicted@sha256:b6d1820a12f80b61The 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_vdauiz7nsgif4sw5)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 17, 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 (8781 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_vdauiz7nsgif4sw5 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/clean-merge-lands-line-guard-on-a-value-neither-branch-predicted GET https://markdownregistry.com/api/v1/blob/b6d1820a12f80b61660ddd4b7f8a9d758af5b59b0c451b5d22ed29d2328ccf17
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.