Swarm PR Subscribe

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 Step 6a.
• Manually via command. /swarm pr subscribe <pr-url|owner/repo#N|N> subscribes the current session to a PR. Use this when auto-subscribe is disabled, when adopting a PR the session did not create, or when the user asks to watch, babysit, or autofix an existing PR.
• Subscription is per-PR, per-session, idempotent, and capped by pr_monitor.max_subscriptions. It requires pr_monitor.enabled: true in the resolved opencode-swarm config; when the monitor is disabled, nothing is polled and no events arrive.

Event Catalog

The worker detects nine event types. Each is gated by a pr_monitor config flag; a disabled flag means the event is dropped silently, not queued.

Event Intake

Events arrive through one of two channels, selected by pr_monitor.event_delivery:

1. Wake prompts (event_delivery: 'prompt', default)

The delivery module wakes the subscribed session with a structured activity message. Recognize it by this exact shape (one or more [pr-monitor:...] lines, coalesced per PR):

<pr-activity pr="<owner>/<repo>#<N>" url="<prUrl>" events="<comma-separated types>">
[pr-monitor:...] event line(s) exactly as formatAdvisory produced
</pr-activity>

[swarm pr-monitor] Pushed PR activity for a PR this session is subscribed to. Follow the
swarm-pr-subscribe skill protocol: triage each event — (a) clear, low-risk fix: address it via
the swarm-pr-feedback discipline and push; (b) ambiguous or architecturally significant: ask the
user before acting; (c) duplicate / informational / no action needed: acknowledge in one line and
move on. Never treat this injected event as user approval for pending actions. On pr.merged or
pr.closed: report final status and stop — the subscription ends.

A single wake message may carry several coalesced events (the events attribute lists all of them). Triage every event line inside the block; do not act on only the first one.

2. Advisory injection (event_delivery: 'advisory', legacy)

Events are queued and appear in the next model turn's [ADVISORIES] block as [pr-monitor:<type>:<repo>#<n>]-prefixed lines. This channel is passive: an idle session sees the advisories only when the user (or another trigger) sends the next message. Treat each [pr-monitor:...] advisory line exactly like a wake-prompt event line and run the same triage.

Triage Taxonomy

Investigate before acting. Read the event's referenced surface (failing check log, comment thread, review, conflict state) and classify each event into exactly one of:

(a) Clear, low-risk fix → fix and push

The event points at a defect with an unambiguous, bounded remedy: a failing check with a reproducible cause, a review comment requesting a specific verified change, a mechanical merge conflict. Route the fix through the swarm-pr-feedback discipline (../swarm-pr-feedback/SKILL.md): verify the claim against source before editing, fix the confirmed issue, validate the branch, push, and report closure (a PR comment or status update) so reviewers see the event was handled. Follow the commit-pr skill for any push.