sync-ado-repos

Syncs GitHub repositories to Azure DevOps project fields via API.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/Vvanlaar/orch --skill sync-ado-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-ado-repos
Source: https://github.com/Vvanlaar/orch/tree/main/.claude/skills/sync-ado-repos
Command: npx skills add https://github.com/Vvanlaar/orch --skill sync-ado-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fs, node-fetch, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of syncing GitHub repositories from a specified organization with Azure DevOps to keep project fields up-to-date.

Core Features & Use Cases

  • Fetches repositories from a GitHub organization, updating or creating a centralized picklist in Azure DevOps.
  • Maintains consistency across multiple processes and work item types by programmatically creating or updating fields.
  • Use case: Streamlining repository management by ensuring the Azure DevOps work item fields always reflect the current GitHub organization repos, facilitating accurate tracking and reporting.

Quick Start

Write a script that reads your GitHub and Azure DevOps credentials, fetches and updates repo lists, and modifies the work item type configurations to include the latest repositories.

Frequently Asked Questions about sync-ado-repos

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

FAQPage Schema
How do I sync GitHub repositories with Azure DevOps project fields?

Syncing GitHub repositories with Azure DevOps project fields involves fetching repos from a specified GitHub organization and updating or creating a centralized picklist in Azure DevOps. This maintains consistency across multiple processes and work item types.

Can I automate updating the Azure DevOps Repository picklist across inherited processes?

Automating the Azure DevOps Repository picklist across inherited processes is achieved by programmatically creating or updating fields. This ensures the picklist is current and integrated across all inherited process work item types.

What credentials do I need to connect GitHub and Azure DevOps for repository synchronization?

Connecting GitHub and Azure DevOps for repository synchronization requires your GitHub and Azure DevOps credentials. The script reads these credentials to authenticate API requests for fetching repo lists and modifying work item type configurations.

Does this repository synchronization approach work for multiple GitHub organizations and work item types?

This repository synchronization approach works for multiple processes and work item types. It fetches repositories from a specified GitHub organization and programmatically updates fields to maintain consistency across your Azure DevOps project configurations.

Why does my Azure DevOps work item tracking show outdated GitHub repositories?

Azure DevOps work item tracking shows outdated GitHub repositories when the picklist is not automatically synced. Running a synchronization script that fetches current repos and updates the Azure DevOps project fields ensures accurate reporting.