azure-pipelines-generator_skill

This skill generates production-ready Azure DevOps pipelines following current best practices, with validation and reusable templates for CI, CD, and
  • HCL

83

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill akin-ozer/cc-devops-skills --skill azure-pipelines-generator

  • .gitignore238 B
  • SKILL.md24.3 KB

Overview

This skill generates production-ready Azure DevOps pipeline YAML that follow current standards, security guidelines, and naming conventions. It produces CI, CD, Docker, Kubernetes, language-specific, and template-based pipelines and validates every output using the azure-pipelines-validator to ensure syntax and best-practice compliance.

How this skill works

The skill asks for project details (language, triggers, environments, registries, and target platforms), then selects appropriate tasks, VM images, caching, and artifact strategies. It constructs YAML with pinned task versions, explicit displayName fields, sensible timeouts, and stage/job hierarchy, and always runs validation; if validation fails it iterates until the pipeline is compliant.

When to use it

  • Creating a new CI pipeline for a repository
  • Building a full multi-stage CI/CD workflow for multiple environments
  • Adding Docker image build and push steps to CI
  • Deploying to Kubernetes or AKS with manifest or Helm flows
  • Converting repeated steps into reusable pipeline templates

Best practices

  • Pin vmImage versions (avoid 'latest') and pin task major versions (e.g., @2)
  • Use displayName for stages, jobs, and key steps to improve readability
  • Implement cache tasks for package managers and Go modules to speed builds
  • Publish test results and use conditions like succeededOrFailed() appropriately
  • Validate every generated YAML with the azure-pipelines-validator and fix issues before merging

Example use cases

  • Generate a Node.js CI pipeline with npm caching, build, test, and test result publishing
  • Create a multi-stage pipeline: Build → Test → Deploy with artifact promotion between stages
  • Build and push Docker images to ACR with image tagging (BuildId and latest) and optional security scan
  • Deploy a containerized app to AKS using KubernetesManifest or Helm with rollout and health checks
  • Create reusable templates for common build steps and reference them from a main pipeline

FAQ

Yes. Every pipeline and template is validated with the azure-pipelines-validator; failures are corrected and re-validated before delivery.

What sources do you use for task inputs and versions?

Local documentation is the primary source (task reference, YAML schema, best-practices). For tasks not covered locally, I prefer context7-style docs or web searches to confirm versions and required inputs.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
azure-pipelines-generator skill by akin-ozer/cc-devops-skills | VeilStrat