orchestrator-monitor

Orchestrate parallel PR reviews and gated merges with bounded concurrency.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/guardian-intelligence/apm2 --skill orchestrator-monitor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-monitor
Source: https://github.com/guardian-intelligence/apm2/tree/main/documents/skills/orchestrator-monitor
Command: npx skills add https://github.com/guardian-intelligence/apm2 --skill orchestrator-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Orchestrates control-loop for PR review and merge operations across multiple agents to keep merge queues short while preserving security and correctness.

Core Features & Use Cases

  • Bounded concurrency: coordinates 1-20 PRs per tick to optimize throughput without overloading reviewers.
  • Evidence-first tracking: per-PR status, blockers, and CI results are recorded to inform decisions.
  • Parallel review launches: simultaneously trigger security and code-quality reviews where slots exist.
  • Auto-merge gating: enables merges only after CI passes and all required reviews are successful.
  • Dashboards and audit: provides a live snapshot of PR states and an auditable decision trail.

Quick Start

Use the orchestrator-monitor to coordinate PR reviews by supplying a space-separated list of PR numbers, or omit to include all open PRs.

Frequently Asked Questions about orchestrator-monitor

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

FAQPage Schema
How do I automate parallel pull request reviews for CI, security, and code-quality?▼

To automate parallel pull request reviews, you can coordinate simultaneous CI, security, and code-quality checks across multiple open PRs. This process uses bounded concurrency to optimize throughput while preserving correctness and preventing reviewer overload.

Can I gate auto-merges until all required CI and security reviews pass?▼

Yes, you can gate auto-merges by enforcing conservative gating rules. Merges are only enabled after CI passes and all required security and code-quality reviews are successful, ensuring safe repository integration.

What is the best way to manage merge queues for multiple open PRs?▼

The best way to manage merge queues is orchestrating a control loop that coordinates 1 to 20 open PRs per tick. This bounded dispatch mechanism keeps queues short without overloading your review infrastructure.

Does orchestrator-monitor generate an audit log for PR merge decisions?▼

Yes, orchestrator-monitor implements evidence-first status tracking and generates an auditable decision log. It records per-PR status, blockers, and CI results to provide a live snapshot and a clear decision trail.

How do I start reviewing all open PRs simultaneously without specifying numbers?▼

To start reviewing all open PRs, simply omit the PR numbers when launching the coordination process. The system will automatically include all open pull requests within its bounded concurrency limits.