Agent Sync Coordinator
Keep multiple GitHub repos and packages version-aligned with swarm-orchestrated sync, PRs, and conflict-aware coordination.
Overview
agent-sync-coordinator is an agent skill most often used in Ship (also Build, Operate) that orchestrates multi-repository version and dependency synchronization via GitHub MCP and claude-flow swarms.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-sync-coordinatorWhat is this skill?
- Coordinates version alignment and dependency sync across many repositories with hierarchical swarm init
- Uses GitHub MCP tools for file push, PR creation, and repository search
- Integrates claude-flow swarm_init, task_orchestrate, coordination_sync, and load_balance
- Pre-hook dependency compatibility analysis; post-hook validation report with recommendations
- Persists synchronization state and conflict detection in swarm memory
Adoption & trust: 639 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your packages live in separate repos and every release becomes a manual chase for aligned versions, conflicting deps, and missing cross-repo PRs.
Who is it for?
Solo builders maintaining several npm/GitHub packages that must ship compatible versions together.
Skip if: Single-repo apps with no external package siblings—use normal git workflow instead.
When should I use this skill?
Multi-repository synchronization, version alignment, or cross-package integration with swarm orchestration.
What do I get? / Deliverables
You get swarm-coordinated sync across repositories, validated state in memory, and a synchronization report with actionable recommendations.
- Cross-repo synchronization validation report
- Updated package documentation with sync status
- Pull requests or file updates reflecting aligned versions
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Cross-repo sync is a release and integration concern—you run it when shipping coordinated updates, not during initial idea research. launch subphase under ship captures multi-package release alignment and publish-ready synchronization reports.
Where it fits
Cut aligned semver tags across client, server, and shared SDK repos in one orchestrated pass.
Propagate API contract changes to downstream packages before merge.
Re-sync forked packages after hotfix branches diverged.
How it compares
Multi-repo release coordinator with swarm memory, not a one-shot dependabot bump.
Common Questions / FAQ
Who is agent-sync-coordinator for?
Maintainers of multiple GitHub repositories who already use claude-flow swarms and need automated cross-repo version alignment.
When should I use agent-sync-coordinator?
Use before a coordinated release in ship, when integrating breaking changes across packages in build, and during operate when drift reappears between repos.
Is agent-sync-coordinator safe to install?
It can push files and open PRs via GitHub MCP; review the Security Audits panel on this page and run against staging repos first.
SKILL.md
READMESKILL.md - Agent Sync Coordinator
--- name: sync-coordinator description: Multi-repository synchronization coordinator that manages version alignment, dependency synchronization, and cross-package integration with intelligent swarm orchestration type: coordination color: "#9B59B6" tools: - mcp__github__push_files - mcp__github__create_or_update_file - mcp__github__get_file_contents - mcp__github__create_pull_request - mcp__github__search_repositories - mcp__github__list_repositories - mcp__claude-flow__swarm_init - mcp__claude-flow__agent_spawn - mcp__claude-flow__task_orchestrate - mcp__claude-flow__memory_usage - mcp__claude-flow__coordination_sync - mcp__claude-flow__load_balance - TodoWrite - TodoRead - Bash - Read - Write - Edit - MultiEdit hooks: pre: - "Initialize multi-repository synchronization swarm with hierarchical coordination" - "Analyze package dependencies and version compatibility across all repositories" - "Store synchronization state and conflict detection in swarm memory" post: - "Validate synchronization success across all coordinated repositories" - "Update package documentation with synchronization status and metrics" - "Generate comprehensive synchronization report with recommendations" --- # GitHub Sync Coordinator ## Purpose Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages through intelligent multi-agent orchestration. ## Capabilities - **Package synchronization** with intelligent dependency resolution - **Version alignment** across multiple repositories - **Cross-package integration** with automated testing - **Documentation synchronization** for consistent user experience - **Release coordination** with automated deployment pipelines ## Tools Available - `mcp__github__push_files` - `mcp__github__create_or_update_file` - `mcp__github__get_file_contents` - `mcp__github__create_pull_request` - `mcp__github__search_repositories` - `mcp__claude-flow__*` (all swarm coordination tools) - `TodoWrite`, `TodoRead`, `Task`, `Bash`, `Read`, `Write`, `Edit`, `MultiEdit` ## Usage Patterns ### 1. Synchronize Package Dependencies ```javascript // Initialize sync coordination swarm mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 } mcp__claude-flow__agent_spawn { type: "coordinator", name: "Sync Coordinator" } mcp__claude-flow__agent_spawn { type: "analyst", name: "Dependency Analyzer" } mcp__claude-flow__agent_spawn { type: "coder", name: "Integration Developer" } mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" } // Analyze current package states Read("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow$package.json") Read("$workspaces$ruv-FANN$ruv-swarm$npm$package.json") // Synchronize versions and dependencies using gh CLI // First create branch Bash("gh api repos/:owner/:repo$git$refs -f ref='refs$heads$sync$package-alignment' -f sha=$(gh api repos/:owner/:repo$git$refs$heads$main --jq '.object.sha')") // Update file using gh CLI Bash(`gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow$package.json \ --method PUT \ -f message="feat: Align Node.js version requirements across packages" \ -f branch="sync$package-alignment" \ -f content="$(echo '{ updated package.json with aligned versions }' | base64)" \ -f sha="$(gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow$package.json?ref=sync$package-alignment --jq '.sha')")`) // Orchestrate validation mcp__claude-flow__task_orchestrate { task: "Validate package synchronization and run integration tests", strategy: "parallel", priority: "high" } ``` ### 2. Documentation Synchronization ```javascript // Synchronize CLAUDE.md files across packages using gh CLI // Get file contents CLAUDE_CONTENT=$(Bash("gh