ops-merge

Orchestrate autonomous PR merges across repositories with fixer agents and safety rules.

22|6|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Lifecycle-Innovations-Limited/claude-ops --skill ops-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-merge
Source: https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-merge
Command: npx skills add https://github.com/Lifecycle-Innovations-Limited/claude-ops --skill ops-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous PR merge orchestration across multiple repositories, coordinating fixers, CI remediation, conflict resolution, and the final merge, with optional dev↔main sync.

Core Features & Use Cases

  • Orchestrates PR queue classification and merging when ready across repos.
  • Dispatches fixer agents to fix CI failures, rebase conflicts, and address review comments.
  • Tracks progress, enforces safety rules, and provides audit-friendly merge workflows.

Quick Start

Run the OPS merge workflow to start evaluating and merging open PRs across your repositories.

Frequently Asked Questions about ops-merge

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

FAQPage Schema
How do I automate PR merging across multiple repositories?

Automating PR merging across multiple repositories involves orchestrating an end-to-end workflow that classifies open PR queues, dispatches fixer agents for CI remediation and conflict resolution, and executes the final merge with safety enforcement.

What is the best way to handle CI failures before a pull request merge?

Handling CI failures before a pull request merge is done by dispatching fixer agents that automatically remediate test failures, address review comments, and rebase conflicts, tracking progress until the PR satisfies safety rules for merging.

Can I automatically resolve merge conflicts in a PR queue?

Automatically resolving merge conflicts in a PR queue is supported by dispatching agent-based fixers that handle conflict resolution and rebase operations, coordinating actions across repositories until the PR is ready for merging.

How do I synchronize dev and main branches during PR orchestration?

Synchronizing dev and main branches during PR orchestration is handled as an optional dev↔main synchronization step, coordinating merges and safety rules across the repository workflow to keep branches aligned.

Does autonomous PR orchestration enforce safety rules and audit trails?

Autonomous PR orchestration enforces safety rules and provides audit-friendly workflows by tracking progress, coordinating fixer agents, and ensuring all merge actions and CI remediation steps are auditable end-to-end.

When should I use an agent-based merge orchestration workflow?

Using an agent-based merge orchestration workflow is ideal when managing multiple repositories with open PR queues, CI failures, and merge conflicts, requiring end-to-end coordination, safety rules, and auditable actions for production-grade automation.