azure-init

Clone all repositories from an Azure DevOps project into a local directory.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Saturate/claude --skill azure-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-init
Source: https://github.com/Saturate/claude/tree/main/skills/azure-init
Command: npx skills add https://github.com/Saturate/claude --skill azure-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a local development environment by cloning all repositories from an Azure DevOps project, enabling rapid workspace setup.

Core Features & Use Cases

  • Find an Azure DevOps project by name or ID and list all repositories.
  • Clone all repositories to a clean, organized local directory with optional nested structure based on repository naming or project structure.
  • Automatically verify prerequisites (Azure CLI with azure-devops extension or MCP) and establish SSH-based cloning with guidance for setup.

Quick Start

Invoke the azure-init skill with a project name to clone all repositories.

Frequently Asked Questions about azure-init

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

FAQPage Schema
How do I clone all repositories from an Azure DevOps project locally?

Cloning all Azure DevOps repositories locally requires using Azure CLI with the azure-devops extension to list project repositories and Git to pull them into an organized local directory. The process supports optional nested folder structures based on repository naming.

What prerequisites do I need to set up a local development workspace from Azure DevOps?

Setting up a local development workspace from Azure DevOps requires the Azure CLI with the azure-devops extension or MCP installed. You also need SSH configured for Git cloning, which the automation process verifies before pulling repositories.

Can I organize cloned Azure DevOps repositories into nested folder structures?

Yes, cloned Azure DevOps repositories can be organized into nested folder structures. The automation applies optional nested directory organization based on repository naming conventions or the original project structure to maintain a clean local workspace.

Does the Azure DevOps bulk cloning process support a dry run?

Yes, the Azure DevOps bulk cloning process supports an optional dry-run capability. This allows you to verify the target repository list and directory structure before actually executing the Git clone operations.

Why use SSH for cloning Azure DevOps repositories instead of HTTPS?

Using SSH for cloning Azure DevOps repositories enables secure, password-less authentication across multiple repositories during batch operations. The automation establishes SSH-based cloning directly and provides setup guidance for initial key configuration.

What is the best way to bootstrap a developer workspace with multiple Azure DevOps repositories?

The best way to bootstrap a developer workspace from Azure DevOps is using an end-to-end automation workflow that parses arguments, normalizes repository naming, and batch clones all project repositories into a clean, organized local directory.