cross-repo-coordination

Coordinate runs-on label migrations across multiple GitHub repositories.

Updated Sep 23, 2025
One-click install
npx skills add https://github.com/Matchpoint-AI/matchpoint-github-runners-helm --skill cross-repo-coordination
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-repo-coordination
Source: https://github.com/Matchpoint-AI/matchpoint-github-runners-helm/tree/main/.claude/skills/cross-repo-coordination
Command: npx skills add https://github.com/Matchpoint-AI/matchpoint-github-runners-helm --skill cross-repo-coordination

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changing GitHub Actions runner configurations often breaks CI/CD across multiple repositories due to mismatched runs-on labels. This Skill prevents stuck jobs and ensures smooth transitions by coordinating updates across all affected repositories.

Core Features & Use Cases

  • Workflow Label Audit: Automatically scan all affected repositories for current runs-on labels.
  • Migration Planning: Guides through zero-downtime (dual runner pools) or coordinated cutover strategies.
  • Automated Workflow Updates: Generates scripts to bulk update runs-on labels across multiple repositories.
  • Use Case: When upgrading your self-hosted GitHub Actions runners, use this Skill to ensure all dependent project repositories (e.g., project-beta-frontend, project-beta-api) are updated with the correct runs-on labels, preventing CI/CD outages.

Quick Start

Use the cross-repo-coordination skill to plan and execute a migration of GitHub Actions runner labels from 'arc-runners' to 'arc-beta-runners' across all project-beta repositories. Provide a summary of affected workflows and a recommended migration strategy.

Frequently Asked Questions about cross-repo-coordination

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

FAQPage Schema
How do I update runs-on labels across multiple GitHub repositories without breaking CI/CD?

Coordinate runs-on label updates across repositories by auditing current labels, planning a migration strategy (dual-pool or cutover), and using scripts to bulk update workflows. This prevents CI/CD outages when changing self-hosted runner configurations.

What's the best way to migrate GitHub Actions runner labels with zero downtime?

Use a dual-pool migration strategy to run both old and new runner labels simultaneously during transition. This allows gradual workflow migration across repositories before decommissioning the legacy pool, ensuring no job failures.

Can I automate scanning and updating runs-on labels across all my project repositories?

Yes. Automated workflow label auditing scans all affected repositories for current runs-on labels, then generates Bash and GitHub CLI scripts to bulk update labels, eliminating manual per-repository changes.

How do I plan a GitHub Actions runner configuration change across multiple repos?

End-to-end planning involves auditing all affected workflows, selecting a migration option (dual-pool for zero-downtime or single cutover), validating label alignment with runnerScaleSetName, and executing verified updates via PR workflows.

What happens if runs-on labels don't match my new runnerScaleSetName?

Mismatched labels cause jobs to hang or fail because runners cannot be assigned. This Skill enforces alignment between runs-on labels and runnerScaleSetName through verification steps and coordinated migration across all project repositories.