Help us improve
Share bugs, ideas, or general feedback.
From devops-skills
Generates Azure DevOps pipeline YAML for CI/CD, including multi-stage workflows, Docker builds, Kubernetes deploys, language-specific setups, and reusable templates.
npx claudepluginhub akin-ozer/cc-devops-skills --plugin devops-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/devops-skills:azure-pipelines-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate production-ready Azure DevOps pipeline YAML with deterministic steps, explicit fallbacks, and clear completion criteria.
docs/best-practices.mddocs/tasks-reference.mddocs/templates-guide.mddocs/yaml-schema.mdexamples/basic-ci.ymlexamples/dotnet-cicd.ymlexamples/go-cicd.ymlexamples/kubernetes-deploy.ymlexamples/multi-stage-cicd.ymlexamples/python-cicd.ymlexamples/template-usage.ymlexamples/templates/build-template.ymlexamples/templates/deploy-template.ymltests/test_template_regressions.pyProvides Azure DevOps YAML pipeline best practices on multi-stage structures, triggers, scheduling, variables, caching, templates, and security for efficient CI/CD.
Designing composable Azure DevOps YAML pipelines. Templates, variable groups, multi-stage, triggers.
Generates production-ready GitLab CI/CD pipelines (.gitlab-ci.yml), stages, and jobs following best practices; validates syntax and compliance for builds, deploys, and scans.
Share bugs, ideas, or general feedback.
Generate production-ready Azure DevOps pipeline YAML with deterministic steps, explicit fallbacks, and clear completion criteria.
Use this skill when the user asks to generate or redesign Azure Pipelines YAML, for example:
azure-pipelines.yml for my Node service."Do not use this skill for validation-only requests. For validation-only work, use azure-pipelines-validator.
Normative keywords:
MUST: requiredSHOULD: default unless user asks otherwiseMAY: optionalDeterministic sequence:
If a step cannot run due to environment limits, use the fallback in that step and continue.
Choose exactly one primary mode:
Mode-to-example mapping:
examples/basic-ci.ymlexamples/multi-stage-cicd.ymlexamples/dotnet-cicd.ymlexamples/python-cicd.ymlexamples/go-cicd.ymlexamples/kubernetes-deploy.ymlexamples/template-usage.yml + examples/templates/*.ymlCollect these before generation:
Safe defaults when missing:
main, developmain onlyubuntu-22.04)$(Build.BuildId)), never deploy latestIf key details are missing, state assumptions explicitly in final output.
Read local references first.
Always read:
docs/yaml-schema.mddocs/best-practices.mdRead conditionally:
docs/tasks-reference.md when selecting tasks/inputsdocs/templates-guide.md only for template-based modeThen read only the closest example(s) from the mode mapping above.
Fallback behavior for missing references:
The final response MUST include:
References usedReferences skipped or missingImpactEscalate beyond local docs only when:
Use this order:
mcp__context7__resolve-library-id -> mcp__context7__query-docs)If network/tools are unavailable, proceed with best-known local guidance and add a residual-risk note.
Apply all items below unless user asks for a narrow snippet.
Security:
Versioning:
vmImage to explicit version, not *-latest.Task@N).@0 is allowed only when that task uses major 0.Reliability:
dependsOn.timeoutInMinutes for long-running jobs.condition rules.environment for deploy stages.Performance:
Cache@2 where it improves dependency install time.Testing/observability:
condition: succeededOrFailed().Maintainability:
displayName for stages/jobs/key steps.Default path (MUST for full pipeline generation):
azure-pipelines-validator.Script fallback if validator skill is unavailable but local validator scripts exist:
bash devops-skills-plugin/skills/azure-pipelines-validator/scripts/validate_azure_pipelines.sh <pipeline-file>
Manual fallback when neither skill nor script can run:
stages -> jobs -> steps)Task@Major)When fallback is used, final response MUST include:
Validation status: Manual fallbackChecks performedResidual riskValidation MAY be skipped only for:
Final response MUST include:
docs/yaml-schema.md, docs/best-practices.md, and examples/multi-stage-cicd.yml.azure-pipelines-validator; fix and re-run.Validation status: Skipped (snippet-only).The execution is complete only when all applicable checks pass: