swarm-pr-subscribe SKILL.md skillA
swarm-pr-subscribe from zaxbyhub/opencode-swarm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zaxbyhub/opencode-swarm/swarm-pr-subscribe@git:20261012.097422cPins git:20261012.097422c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zaxbyhub/opencode-swarm
- Path
.opencode/skills/swarm-pr-subscribe/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261012.097422c, committed Oct 12, 2026
- First version recorded
- Jul 2, 2026
- Size
- 8,982 bytes
- Repository stars
- 518
- License
- MIT
Monitor a pull request after creation and act autonomously on pushed PR activity. Use when subscribing to a PR after opening it, when asked to watch, babysit, or autofix a PR until merge, or when a <pr-activity> wake message or [pr-monitor:...] advisory arrives for a subscribed PR. Owns event triage (fix / ask / skip), bounded-retry escalation, and terminal-state cleanup.
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
# Swarm PR Subscribe Use this skill to keep a pull request healthy after it is opened, without the user having to relay every review comment or CI failure by hand. The PR monitor worker polls subscribed PRs in the background and pushes detected events into the subscribed session; this skill defines how to receive those events, triage them, and act. This is the final hop of the PR lifecycle: **commit-pr → swarm-pr-review → swarm-pr-feedback → swarm-pr-subscribe.** `commit-pr` publishes the PR, `swarm-pr-review` discovers new findings, `swarm-pr-feedback` closes known feedback, and `swarm-pr-subscribe` keeps watching the PR — routing fresh events back through the feedback discipline — until the PR is merged or closed. > **Cross-reference**: For ongoing CI-status tracking across multiple PRs (not just one PR's feedback), use the `swarm-ci-monitor` skill instead. ## When To Subscribe - **Automatically after PR creation.** When `pr_monitor.enabled` and `pr_monitor.auto_subscribe_on_pr_create` (default `true`) are set, the subscription is created automatically right after `gh pr create` succeeds — no command needed. This is the standard path from the commit-pr skill's …
Read the whole file at its exact version.
How to install
mdr add zaxbyhub/opencode-swarm/swarm-pr-subscribe@sha256:fa81d97bba10b275The line at the top of this page pins the label git:20261012.097422c, 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_puijbjos6uvgl2zr)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 2, 2026 and Oct 12, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.097422c latest | 2026-10-12 | 097422c | 8,982 B | A | view · diff |
| git:20260919.88fa763 | 2026-09-19 | 88fa763 | 8,968 B | A | view · diff |
| git:20260919.34272d0 | 2026-09-19 | 34272d0 | 8,968 B | A | view · diff |
| git:20260712.873105b | 2026-07-12 | 873105b | 8,932 B | A | view · diff |
| git:20260711.5972d3e | 2026-07-11 | 5972d3e | 8,785 B | A | view · diff |
| git:20260702.34cd3c5 | 2026-07-02 | 34cd3c5 | 8,762 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 (8982 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
zaxbyhub/opencode-swarm · 518 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_puijbjos6uvgl2zr GET https://markdownregistry.com/api/v1/resolve?ref=zaxbyhub/opencode-swarm/swarm-pr-subscribe GET https://markdownregistry.com/api/v1/blob/fa81d97bba10b2752880755d7b48cbdaf99585041661df02bf2bc6304c7c92ed
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.
More from zaxbyhub/opencode-swarm
Every file in zaxbyhub/opencode-swarm