swarm-pr-subscribe

Monitor OpenCode Swarm pull requests and resolve low-risk CI failures automatically.

437|45|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill swarm-pr-subscribe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-pr-subscribe
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/swarm-pr-subscribe
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill swarm-pr-subscribe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking pull request reviews, CI failures, and comment threads is tedious and error-prone, often leading to stalled PRs or missed issues that delay merges.

Core Features & Use Cases

  • Automated PR Monitoring: Subscribes to pull requests automatically after creation or on demand, polling for CI status changes, new comments, review activity, and merge conflicts.
  • Smart Event Triage: Classifies incoming PR events into low-risk fixes to apply automatically, ambiguous changes requiring user approval, or informational updates to acknowledge.
  • Use Case: For development teams using OpenCode Swarm, eliminate the need to manually relay every review comment or CI failure, keeping PRs healthy and moving toward merge without constant manual oversight.

Quick Start

Use the swarm-pr-subscribe skill to automatically monitor your open pull request, fix low-risk issues like failing CI checks or requested review changes, and alert you only when you need to make a product or architectural decision.

Frequently Asked Questions about swarm-pr-subscribe

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

FAQPage Schema
How do I automate pull request monitoring for CI failures and merge conflicts?

Automated pull request monitoring tracks CI status changes, new comments, and merge conflicts via background polling. It identifies low-risk issues and applies fixes automatically, keeping PRs healthy without manual oversight.

How does smart event triage handle new review comments on AI-generated code?

Smart event triage classifies incoming PR events into low-risk fixes to apply automatically, ambiguous changes requiring user approval, or informational updates to acknowledge, ensuring safe handling of AI-generated code changes.

Can I use PR automation tools with OpenCode Swarm to fix requested review changes?

PR automation tools work with OpenCode Swarm to automatically resolve requested review changes. They apply bounded-retry error handling for fix attempts and alert you only when product or architectural decisions are needed.

What is the best way to prevent stalled pull requests caused by missed CI failures?

Preventing stalled pull requests requires automated polling for CI failures and review activity. The system applies bounded-retry error handling to auto-fix issues and performs terminal state cleanup when PRs merge or close.

Does automated PR triage support configurable notifications for different event types?

Automated PR triage supports configurable notification gates for each event type. This ensures you receive alerts only for ambiguous changes requiring approval while low-risk fixes are resolved silently in the background.

When should I not use autonomous merge conflict resolution for my pull requests?

You should not use autonomous merge conflict resolution for ambiguous changes requiring user approval. The triage taxonomy specifically routes complex architectural decisions and high-risk conflicts to human review instead of auto-fixing.