From ado-aw
Compiles ado-aw agent files to Azure DevOps pipeline YAML and validates them via CLI and MCP tools. Use when asked to compile, check validity, verify pipeline-source parity, or inspect compiled IR/dependency graphs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ado-aw:compile-and-validateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compile and validate an ado-aw agentic workflow. This skill is CLI- and
Compile and validate an ado-aw agentic workflow. This skill is CLI- and MCP-driven; it does not fetch a remote playbook.
Confirm the ado-aw compiler is installed (ado-aw --version).
Compile with the CLI (mutates the .lock.yml on disk):
ado-aw compile <agent-file.md> — compile one file.ado-aw compile — auto-discover and recompile all detected pipelines.ado-aw check <pipeline.lock.yml> — verify a compiled pipeline still
matches its source Markdown (good for CI parity checks).Validate and explain with the read-only MCP tools (no mutation):
lint_workflow — structural lint checks; resolve every finding.inspect_workflow — the public PipelineSummary (schema_version = 1).graph_summary / graph_dump — the resolved dependency graph
(text or Graphviz DOT).step_dependencies — upstream/downstream traversal for a step or job id.step_outputs — declared outputs and their consumers.Treat the workflow as "valid" only when compile succeeds and
lint_workflow is clean. Recompile after any YAML front-matter change.
The user's request: $ARGUMENTS
npx claudepluginhub githubnext/ado-aw --plugin ado-awCreates a new ado-aw agentic Azure DevOps pipeline from scratch. Use when authoring a brand-new AI-powered ADO pipeline as a Markdown agent file. Results in a clean compile and lint.
Generates Azure DevOps pipeline YAML for CI/CD, including multi-stage workflows, Docker builds, Kubernetes deploys, language-specific setups, and reusable templates.
Generates and manages AgentOps release-readiness workflows: PR eval gates, evidence artifacts, and deploy handoffs to azd or Foundry.