subagent-reports-complete-but-pr-unmerged SKILL.md skillA
subagent-reports-complete-but-pr-unmerged 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/subagent-reports-complete-but-pr-unmerged@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/subagent-reports-complete-but-pr-unmerged/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed Sep 17, 2026
- First version recorded
- May 13, 2026
- Size
- 10,043 bytes
- Repository stars
- 3
- License
- MIT
Catch the systematic gap between sub-agent "completed" status and the actual end state of a PR-merge orchestration task. Use when: (1) you've dispatched multiple parallel sub-agents (general-purpose or specialist) to open + review + merge PRs, (2) the parent receives `<task-notification>` with `status: completed` but the sub-agent's last action was waiting on CI, addressing a review finding, or pushing a rebased branch, (3) you're tempted to mark the parent task done based on the completion…
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
# Sub-Agent Reports "Completed" While PR Is Still OPEN ## Problem You dispatch 3-5 parallel sub-agents to open + review + merge PRs that close GitHub issues. Each agent's brief explicitly says "wait for green CI, add `auto-deploy` label, squash-merge, delete branch, verify issue auto-closes." The agents work, push PRs, then return `<task-notification status: completed>`. Several of those PRs are still OPEN. CI was still in-progress when the agent terminated. Or a reviewer found a P1 and the agent fixed it but stopped before re-running CI. Or the agent post-rebased and pushed but didn't merge. The parent, reading "completed," marks its TaskList task done. Hours later you realize 3 of 5 PRs never landed. This is **systematic**, not occasional. In one session (`scan-bugs-parallel`, 2026-05-08, this repo) **4 of 4** sub-agents stopped before final merge: - Wave1-G PR #527: agent posted P1 review, then stopped. Parent had to dispatch a continuation agent to fix + merge. - Wave1-E PR #528: agent's final summary "Now I'll continue with the rest of the workflow (CI, auto-deploy label, merge)" — but the message ended there. PR was OPEN with green CI. Parent merged. …
Read the whole file at its exact version.
How to install
mdr add wan-huiyan/agent-traffic-control/subagent-reports-complete-but-pr-unmerged@sha256:4783302a1b101e08The 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_iex5k5hkisscwwpr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 13, 2026 and Sep 17, 2026, about one every 42 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-09-17 | e5ca372 | 10,043 B | A | view · diff |
| v1.0.0 | 2026-08-12 | 9a8e5a8 | 9,120 B | A | view · diff |
| v1.0.0 | 2026-07-08 | f1254dd | 9,096 B | A | view · diff |
| v1.0.0 | 2026-05-13 | 07472bf | 9,030 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 (10043 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_iex5k5hkisscwwpr GET https://markdownregistry.com/api/v1/resolve?ref=wan-huiyan/agent-traffic-control/subagent-reports-complete-but-pr-unmerged GET https://markdownregistry.com/api/v1/blob/4783302a1b101e088c00dbfae55398b4cb5ecae108bcb2c834155f1de5baa60a
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.