working-tree-edits-stranded-on-squash-merge SKILL.md skillA
working-tree-edits-stranded-on-squash-merge 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/working-tree-edits-stranded-on-squash-merge@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/working-tree-edits-stranded-on-squash-merge/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.0, committed Jul 8, 2026
- First version recorded
- May 29, 2026
- Size
- 7,327 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and prevent "I made the fix but it's not on main" cases where the fix was applied in the working tree via Edit / Write but never `git add`ed before the squash-merge. Use when: (1) you squash-merged a PR and the user reports the issue is back, (2) `git status` after the merge shows uncommitted changes for files you remember editing during the PR's acceptance pass, (3) a follow-up `git diff origin/<base>` against the merged branch surfaces edits that should have been in the PR. Root…
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
# Working-tree edits stranded by a squash-merge ## Problem You're iterating on a PR through an acceptance pass. The user surfaces a bug; you make an Edit() call; the bug is fixed locally; the user confirms; you move on to the next bug. A few iterations later you squash-merge the PR. The user reloads the page and says "the bug is back." The fix is sitting in your working tree, never staged, never committed. The squash captured everything *committed* on the branch — but Edit() and Write() don't auto-stage. When you did `git add <other_file>` for the follow-up bug, only that file went into the commit; the earlier Edit'd file stayed in the working tree as a modified-but-uncommitted change. After merge: `git status` shows `M <file_you_edited>`, the merged squash on `<base_branch>` has the old content, and the user sees the bug return. ## Context / Trigger Conditions All of these together strongly indicate this pattern: 1. You used Edit() or Write() on a file during an interactive PR-review pass (i.e. you applied the fix to "make the live server / preview reflect it" for the user to verify, but didn't think of it as a commit-worthy unit). …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/working-tree-edits-stranded-on-squash-merge@sha256:9eda90a4cb0f9b27The 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_bog5cqu27to35lws)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Jul 8, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-07-08 | f1254dd | 7,327 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 7,296 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 (7327 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_bog5cqu27to35lws GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/working-tree-edits-stranded-on-squash-merge GET https://markdownregistry.com/api/v1/blob/9eda90a4cb0f9b27d4953842ba5aef43cc8162c2dc5189e6735a7250a3c81b60
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.