gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes SKILL.md skillA
gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes 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/gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes@v1.1.1Pins v1.1.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/gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes/SKILL.md- Versions recorded
- 3
- Latest version
- v1.1.1, committed Aug 6, 2026
- First version recorded
- May 29, 2026
- Size
- 11,803 bytes
- Repository stars
- 3
- License
- MIT
Diagnose and recover from two adjacent `gh pr merge` failure modes that masquerade as merge conflicts. Use when: (1) `gh pr merge --squash` (or `--merge`) errors with "To have the pull request merged after all the requirements have been met, add the `--auto` flag" AND "Run the following to resolve the merge conflicts locally" even though you just pushed a clean resolution; (2) `gh pr view <N> --json mergeable,mergeStateStatus` returns `MERGEABLE` + `UNSTABLE` rather than `MERGEABLE` + `CLEAN`…
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
# `gh pr merge` UNSTABLE state + branch-delete recovery ## Problem Two adjacent failure modes that read as "merge conflicts" but aren't: ### Failure A: `gh pr merge` rejects with "conflicts" when there are none You push a clean resolution of merge conflicts, GitHub shows the PR as MERGEABLE, and yet: ``` $ gh pr merge 915 --squash To have the pull request merged after all the requirements have been met, add the `--auto` flag. Run the following to resolve the merge conflicts locally: gh pr checkout 915 && git fetch origin main && git merge origin/main ``` The first line is the actual hint; the second is misleading boilerplate. The real cause is `mergeStateStatus: UNSTABLE` — branch protection or CI checks are pending. `gh` can't merge yet because the repo's rules aren't satisfied, not because of file-level conflicts. ### Failure B: PR auto-closes if you delete the remote branch right after Failure A Common pattern: previous PR on the same branch merged cleanly with `gh pr merge <N> --squash`. You then do `git push origin --delete <branch>` to clean up. Habit kicks in for the next PR — you run `gh pr merge` (gets Failure A above), notice the "conflicts" warning, run …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes@sha256:7ca1bb3046f428d9The line at the top of this page pins the label v1.1.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_43row5npvfojrbg6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 29, 2026 and Aug 6, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.1 latest | 2026-08-06 | a81b2a1 | 11,803 B | A | view · diff |
| v1.1.0 | 2026-07-08 | f1254dd | 11,648 B | A | view · diff |
| v1.0.0 | 2026-05-29 | 059688a | 9,098 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 (11803 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_43row5npvfojrbg6 GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes GET https://markdownregistry.com/api/v1/blob/7ca1bb3046f428d95e500d160a02546ad2c94042d5e4de0672e48decc9336bb3
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.