ado-pipeline-best-practices

Q: How do I install ado-pipeline-best-practices?

Run npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ado-pipeline-best-practices/ (personal) or .claude/skills/ado-pipeline-best-practices/ (project).

by josiahsiegelDevOps & Cloud

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.

Installs: 178
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads ado-pipeline-best-practices automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Azure Pipelines Best Practices

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

Core Review Procedure

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

Pipeline Structure

Multi-Stage Pipelines:

# 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

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:
      include: [main]
    always: false  # Only if code changed

Variable Management

Hierarchy:

Pipeline-level variables (az devops YAML)
Variable groups (shared across pipelines)
Azure Key Vault (secrets)
Runtime parameters (user input)

Security:

Never hardcode secrets
Use Key Vault for sensitive data
Mark secrets in variable groups
Secrets are automatically masked in logs

Caching

Implement caching for:

Package dependencies (npm, pip, NuGet, Maven)
Docker layers
Build outputs

Impact:

Faster builds (up to 90% reduction)
Reduced network usage
Lower costs

Templates

Use templates for:

Reusable build patterns
Standardized deployment steps
Consistent security scanning
Company-wide best practices

Benefits:

DRY (Don't Repeat Yourself)
Centralized updates
Consistent processes

Security Practices

Essential:

Code scanning (SAST, dependency)
Container image scanning
Secret scanning
Compliance checks
Branch protection policies
Required approvals

Performance

Optimize:

Parallelize independent jobs
Use caching extensively
Shallow git clones (fetchDepth: 1)
Appropriate agent pools
Clean up artifacts

Monitoring

Track:

Build success rates
Build durations
Test pass rates
Deployment frequency
Mean time to recovery (MTTR)

References and Pairings

Use Microsoft Azure Pipelines YAML schema documentation for task syntax and newly released features.
Pair with workload-identity/OIDC guidance when replacing service principal secrets.
Pair with security scanning guidance when adding SAST, dependency, container, or IaC checks.

Always verify best practices against latest Azure DevOps documentation.

FAQ

What does the ado-pipeline-best-practices skill do?

How do I install ado-pipeline-best-practices?

Run npx skills add https://github.com/josiahsiegel/claude-plugin-marketplace --skill ado-pipeline-best-practices in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ado-pipeline-best-practices/ (personal) or .claude/skills/ado-pipeline-best-practices/ (project).

Which AI agents can use ado-pipeline-best-practices?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ado-pipeline-best-practices safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ado-pipeline-best-practices?

It is published by josiahsiegel in josiahsiegel/claude-plugin-marketplace. It has 178 recorded installs.