sync-coordinator

Synchronizes versions, dependencies, and documentation across multiple GitHub repositories using swarm orchestration.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill sync-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-coordinator
Source: https://github.com/ruvnet/claude-flow/tree/main/.agents/skills/agent-sync-coordinator
Command: npx skills add https://github.com/ruvnet/claude-flow --skill sync-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping versions, dependencies, and documentation aligned across multiple related repositories (such as claude-code-flow and ruv-swarm) is error-prone manual work. This Skill coordinates multi-repository synchronization with conflict detection, validation testing, and automated pull request creation.

Core Features & Use Cases

  • Version & Dependency Alignment: Analyzes package.json files across repositories and aligns Node.js engine requirements and dependency versions.
  • Documentation Synchronization: Propagates CLAUDE.md and other shared docs from a source of truth to target packages while preserving package-specific sections.
  • Cross-Package Integration: Pushes coordinated multi-file changes, runs integration test matrices, and creates pull requests via GitHub MCP tools or the gh CLI.
  • Use Case: When releasing a new feature that touches both claude-code-flow and ruv-swarm, use this Skill to align package versions, sync documentation, run cross-package tests, and open a single integration PR.

Quick Start

Ask the agent to synchronize the package.json versions and CLAUDE.md documentation between the claude-code-flow and ruv-swarm repositories and open a pull request with the changes.

Frequently Asked Questions about sync-coordinator

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

FAQPage Schema
How do I synchronize package.json versions across multiple repositories?

Initialize a coordination swarm, read each repository's package.json, align engine and dependency versions to the highest common requirement, then push the updated files on a sync branch and open a pull request using GitHub MCP tools or the gh CLI.

How to keep CLAUDE.md documentation consistent across packages?

Designate one file as the source of truth, fetch its content via the GitHub API, and update target repositories on a sync branch. Package-specific sections are preserved through a customSections mapping while shared content stays identical.

Does this work with the GitHub CLI instead of MCP tools?

Yes. The Skill demonstrates both approaches: mcp__github__push_files for batch updates and gh api/gh pr create commands for branch creation, file updates, and pull requests when MCP GitHub tools are unavailable.

What happens when a synchronization conflict or test failure occurs?

The Skill spawns a recovery swarm with monitor, analyzer, and developer agents. It supports automated rollback on critical failures, incremental sync retries, and stores recovery state in swarm memory for persistence.

What are the limitations of swarm-based repository synchronization?

It depends on the claude-flow MCP server and GitHub API access, so it cannot run fully offline. Complex merge conflicts may still require manual intervention at designated intervention points.