azure-pipelines-generator

Azure Pipelines Generator

Overview

Generate production-ready Azure DevOps Pipeline configurations following current best practices, security standards, and naming conventions. After generating any complete pipeline file, always validate it using the devops-skills:azure-pipelines-validator skill, fix any reported issues, and re-validate before presenting to the user. Skip validation only for partial snippets, documentation examples, or when the user explicitly requests it.

Philosophy

• Generate pipelines that are deterministic: pin every image, task and runtime version.
• Keep secrets out of YAML; reference service connections, variable groups or Key Vault instead.
• Prefer reusable templates over long inline pipelines, and validate every complete file before delivery.

When to Use

• Creating or updating an azure-pipelines.yml for build, test or deploy.
• Defining multi-stage deployments with environments, variable groups and service connections.
• Writing Docker build and Kubernetes/AKS deployment pipelines.
• Producing reusable step, job or stage templates and the pipelines that consume them.

When Not to Use

• Reviewing or linting an existing pipeline without changing it: use the validator skill alone.
• Targeting other CI systems such as GitHub Actions, GitLab CI or Jenkins.
• Classic (UI-based) release pipelines that have no YAML definition.
• Provisioning the Azure DevOps organisation, agents or service connections themselves.

Core Capabilities

1. Basic CI Pipelines

Read references/yaml-schema.md, references/best-practices.md, references/tasks-reference.md, and assets/examples/basic-ci.yml.

Example:

trigger:
  branches:
    include:
    - main
    - develop

pool:
  vmImage: 'ubuntu-22.04'

variables:
  buildConfiguration: 'Release'

steps:
- task: NodeTool@0
  displayName: 'Install Node.js'
  inputs:
    versionSpec: '20.x'

- task: Cache@2
  displayName: 'Cache npm packages'
  inputs:
    key: 'npm | "$(Agent.OS)" | package-lock.json'
    path: $(Pipeline.Workspace)/.npm

- script: npm ci --cache $(Pipeline.Workspace)/.npm
  displayName: 'Install dependencies'

- script: npm run build
  displayName: 'Build application'

- script: npm test
  displayName: 'Run tests'

- task: PublishTestResults@2
  condition: succeededOrFailed()
  inputs:
    testResultsFormat: 'JUnit'
    testResultsFiles: '**/test-results.xml'