cross-repo-coordination

The cross-repo-coordination skill is a specialized engineering utility designed to manage the synchronization of GitHub Actions runner labels across multiple project-beta repositories. In a microservices or multi-repo architecture, decoupling runner infrastructure from workflow definitions frequently leads to 'queued' job states when runnerScaleSetName values are modified in Helm charts or ArgoCD applications. This agent automates the audit of .github/workflows/ files to identify discrepancies, generates migration plans—supporting both zero-downtime dual-pool strategies and rapid cutover deployments—and executes automated PR creation using shell-based patching to align infrastructure changes with CI/CD execution environments.

• Performs automated audits of workflow files to detect outdated runs-on labels across multiple Git repositories.

• Generates migration documentation and impact analysis for infrastructure changes related to arc-beta-runners or custom runner pools.

• Supports multi-phase transition strategies including dual-pool deployment (blue-green) and immediate synchronization updates.

• Automates shell-based patching of YAML workflow files using sed and git-cli to update runner identifiers efficiently.

• Provides verification tools to check runner health, label registration, and active job status using GitHub CLI (gh).

• Ideal for DevOps engineers and platform team members managing Rackspace Spot instances or Kubernetes-based runner controllers.

• Inputs include the target runnerScaleSetName and the repository names; outputs include migration PRs, status reports, and validation logs.

• Constraints: Requires write access to repository workflows and assumes standardized directory structures for .github/workflows/.

• Recommended for use during infrastructure upgrades, moving from standard ubuntu-latest runners to self-hosted ARC runners, or adding specialized runner pools with hardware constraints like GPU support.

• Integrates tightly with ArgoCD and Helm-based GitOps workflows to ensure that infrastructure as code (IaC) remains consistent with application-level CI configurations.