gh-squash-merge-closes-only-one-issue SKILL.md skillA
gh-squash-merge-closes-only-one-issue 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-squash-merge-closes-only-one-issue@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/gh-squash-merge-closes-only-one-issue/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0.0, committed Aug 11, 2026
- First version recorded
- May 13, 2026
- Size
- 6,589 bytes
- Repository stars
- 3
- License
- MIT
GitHub auto-close on squash-merge only catches ONE issue per PR even when the PR title/body says "Closes #447, #448, #449, #450". The first issue closes; the rest stay OPEN. Use when: (1) you opened a PR with a title or body listing multiple "Closes #X, #Y, #Z" references, (2) the PR squash-merged successfully (`gh pr view N --json state` = MERGED), (3) `gh issue list --state open` shows some of the referenced issues are still OPEN. Root cause: GitHub's auto-close keyword parser binds one…
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
# GitHub squash-merge auto-closes only one issue per PR ## Problem You shipped a fix PR that addresses 4 filed issues. PR title: > `fix(dashboard): wire /actions segment tiles + plug 4 audit P0s (closes #447, #448, #449, #450)` PR body opens with: > Closes #447, #448, #449, #450 — the four template/route P0s from the audit. PR squash-merges cleanly. CI green, branch deleted. You move on. Later: `gh issue list --state open` shows `#448`, `#449`, `#450` still OPEN. Only `#447` got auto-closed. You spend a confused minute checking whether the fix actually shipped (it did) before realising the issues never closed. ## Context / Trigger Conditions All of: 1. PR title or body includes a comma-separated `Closes #X, #Y, #Z` (or `Fixes`, `Resolves`) reference. 2. PR was **squash-merged** (regular merge has slightly different parsing but the same gotcha applies). 3. After merge: `gh pr view N --json state` returns `MERGED`, but `gh issue view #Y` returns `OPEN` for the second-and-later issues. 4. The first issue in the comma list IS closed correctly — proves your "Closes" keyword wasn't malformed. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-issue@sha256:e961acb944da0c95The 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_cdp73etjtpe3lh6s)
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 Aug 11, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-11 | f274e4b | 6,589 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 6,588 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 6,123 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 (6589 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_cdp73etjtpe3lh6s GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/gh-squash-merge-closes-only-one-issue GET https://markdownregistry.com/api/v1/blob/e961acb944da0c95e8e09d597d41b780106e3be3b0664486298314757211caf0
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.