swarm-pr-subscribe

Monitors subscribed pull requests and triages CI failures, reviews, and merge events autonomously.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pr-subscribe-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-pr-subscribe
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/swarm-pr-subscribe
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pr-subscribe-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After opening a pull request, developers must manually watch for CI failures, review comments, and merge conflicts. This Skill subscribes a session to a PR, receives pushed activity events from a background polling worker, and autonomously triages each event so the PR stays healthy until merge without constant user relaying. ## Core Features & Use Cases - Event-driven PR monitoring: Detects nine event types (CI failure/success, new comments, review approvals or change requests, merge conflicts, merged/closed) via wake prompts or advisory injection, each gated by configurable pr_monitor flags. - Structured triage taxonomy: Classifies every event as (a) clear low-risk fix routed through the swarm-pr-feedback discipline, (b) ambiguous or architecturally significant issue escalated to the user, or (c) informational noise acknowledged quietly. - Bounded retries and terminal cleanup: Applies a 3-strike rule per failing check before escalating with a diagnosis, and automatically ends subscriptions on pr.merged or pr.closed. - Use Case: After gh pr create opens a PR, the session auto-subscribes; when CI fails overnight, the worker wakes the session, the fix is verified, pushed, and reported — all without the user relaying the failure. ## Quick Start Subscribe this session to my open pull request and autonomously fix any CI failures or review comments until it merges.

Frequently Asked Questions about swarm-pr-subscribe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically monitor a GitHub pull request for CI failures?

Subscribe the session to the PR with /swarm pr subscribe <pr-url|owner/repo#N|N>, or let auto-subscribe handle it after gh pr create when pr_monitor.auto_subscribe_on_pr_create is true. A background worker then polls the PR and pushes events like pr.ci.failed into the session for triage.

How to auto-fix PR review comments without manual intervention?

Clear, low-risk findings from review comments are classified as triage category (a) and routed through the swarm-pr-feedback discipline: verify the claim against source, fix it, validate the branch, push, and report closure. Ambiguous or architecturally significant comments are escalated to the user instead of being guessed at.

What PR events can the monitor detect and notify about?

Nine event types are detected: pr.ci.failed, pr.ci.passed, pr.new.comment, pr.review.changes_requested, pr.review.approved, pr.merge.conflict, pr.merge.conflict_resolved, pr.merged, and pr.closed. Each is gated by a pr_monitor config flag, and merged or closed are terminal events that end the subscription.

Does PR monitoring stop automatically after merge?

Yes. On pr.merged or pr.closed the skill reports final status and stops, with auto_unsubscribe_on_merge and auto_unsubscribe_on_close both defaulting to true. You can also stop early at any time with /swarm pr unsubscribe.

What happens when automated PR fixes keep failing CI?

A 3-strike rule applies per distinct failing check or finding: after three consecutive failed fix attempts, the skill stops pushing and escalates to the user with a diagnosis covering what was tried, the evidence from each attempt, and the best current hypothesis.