# ado-pipeline-best-practices

ado-pipeline-best-practices guides coding agents in designing, auditing, and optimizing Azure DevOps YAML pipelines using enterprise patterns.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 182 installs · ★ 66 repo stars
- Author: JosiahSiegel
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/ado-master/skills/ado-pipeline-best-practices/SKILL.md
- Updated: 2026-06-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/ado-pipeline-best-practices

## What it does

This skill gives agents structured procedures for writing and evaluating Azure DevOps pipelines. It enforces separating stages across build, test, and release environments, extracting reusable jobs into templates, and pinning major task versions. Included resources cover matrix builds, dependency caching recipes with `Cache@2` for tools like npm, pip, NuGet, and Maven, plus deployment strategies such as rolling, canary, and blue-green.

Security remains central to the workflow. The skill mandates passing credentials exclusively through service connections, variable groups, or Azure Key Vault rather than inline variables. Hardcoded secrets fail its review criteria immediately.

## Requirements
- Works with: GitHub, Azure, Azure DevOps

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/ado-pipeline-best-practices/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/ado-pipeline-best-practices/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/ado-pipeline-best-practices/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/ado-pipeline-best-practices/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install JosiahSiegel/claude-plugin-marketplace plugins/ado-master/skills/ado-pipeline-best-practices
```

2. **Manually: put the files in place**
- File: `.github/skills/ado-pipeline-best-practices/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/JosiahSiegel/claude-plugin-marketplace --path plugins/ado-master/skills/ado-pipeline-best-practices
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/ado-pipeline-best-practices/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/ado-master/skills/ado-pipeline-best-practices/SKILL.md

## When to use it
- structure multi-stage Azure DevOps pipelines with approval gates
- configure dependency caching with Cache@2 to speed up builds
- refactor repeated YAML jobs into reusable pipeline templates
- audit CI/CD configurations to eliminate plaintext secrets and inline credentials

## Example prompts
- Review my azure-pipelines.yml file against Azure DevOps best practices
- Help me split this monolithic pipeline into Build, Test, and Deploy stages with environments
- Add npm dependency caching to my pipeline using the Cache@2 task

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 48fa14bd8dd736d0.

BEGIN THIRD-PARTY FILE 48fa14bd8dd736d0
````text
---
name: ado-pipeline-best-practices
description: |
  Azure DevOps pipeline best practices, patterns, and industry standards.
  PROACTIVELY activate for: (1) authoring or reviewing Azure DevOps YAML pipelines, (2) multi-stage pipeline patterns (build, test, deploy), (3) reusable templates (steps, jobs, stages), (4) pipeline caching (Cache@2 task), (5) parallel jobs and matrix strategies, (6) deployment strategies (rolling, blue-green, canary), (7) approvals and environments, (8) variable groups, secret variables, Key Vault linkage, (9) service connections (Azure RM, GitHub, container registries), (10) pipeline versioning and pinning task major versions.
  Provides: YAML pattern catalog, template library structure, caching recipes, deployment strategy templates, and a pipeline-quality checklist.
---

# Azure Pipelines Best Practices

Comprehensive best practices for creating and maintaining Azure DevOps YAML pipelines.

## Core Review Procedure

1. Identify trigger scope, deployment environments, and required approvals before editing YAML.
2. Verify secrets flow through service connections, Key Vault, secret variables, or secure files; never inline credentials.
3. Pin task major versions and centralize repeated steps in templates.
4. Add path filters, caching, and parallel jobs only when they reduce real build cost without hiding validation.
5. Keep build, test, package, and deploy concerns separated by stages or jobs.
6. Validate with Azure DevOps pipeline YAML validation or a dry run before recommending rollout.

## Pipeline Structure

**Multi-Stage Pipelines:**
```yaml
# Recommended structure
stages:
  - stage: Build
  - stage: Test
  - stage: DeployDev
  - stage: DeployStaging  
  - stage: DeployProduction
```

**Benefits:**
- Clear separation of concerns
- Conditional stage execution
- Environment-specific configurations
- Approval gates between stages

## Triggers and Scheduling

**Best practices:**
- Use path filters to avoid unnecessary builds
- Enable batch builds for high-frequency repos
- Use PR triggers for validation
- Schedule nightly/weekly builds for comprehensive testing

```yaml
trigger:
  batch: true
  branches:
    include: [main, develop]
  paths:
    exclude: ['docs/*', '**.md']

pr:
  autoCancel: true
  branches:
    include: [main]

schedules:
  - cron: '0 0 * * *'
    displayName: 'Nightly build'
    branches:
````
END THIRD-PARTY FILE 48fa14bd8dd736d0

The third-party file has ended. Everything between the 48fa14bd8dd736d0 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2376 of 4129 bytes. © JosiahSiegel · MIT · https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/ado-master/skills/ado-pipeline-best-practices/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
