Agent skills for working with Azure Pipelines
npx claudepluginhub lbussell/azurepipelinestoolInteract with Azure Pipelines from the terminal
azp - Azure Pipelines ToolA CLI for interacting with Azure Pipelines from the terminal.
Install the tool globally:
dotnet tool install -g azp
Install agent skill (interactive):
dnx azp -y -- install-skill
azd auth login| Command | Purpose |
|---|---|
azp list | List all pipelines in the current repository |
azp info <path> | Show pipeline details: variables, parameters, metadata |
azp check <path> | Preview expanded YAML (dry run with template parameters) |
azp run <path> | Queue a pipeline run with parameters, variables, and stage skips |
azp status <id> | Show run status as a tree of stages, jobs, and tasks |
azp cancel <id> | Cancel a running pipeline build |
azp wait <id> | Poll until a run completes, with optional failure exit code |
azp logs <id> <logId> | Download logs for a specific task from a run |
azp llmstxt | Print comprehensive tool documentation |
azp install-skill | Install the agent skill to a local or user directory |
<path> is a relative path to the pipeline YAML file.
<id> is a numeric build ID or a full Azure DevOps build results URL.
[!NOTE] Commands requiring the
pathargument require you to runazpfrom within a Git repo that has a remote pointing to Azure DevOps.azpuses your git remotes to infer Azure DevOps organization, project, and repo context to find pipelines associated with your repo.
Commands chain together in natural workflows.
# Discover pipelines in the current repo
azp list
# Inspect a pipeline's variables and parameters
azp info path/to/pipeline.yml
# Validate YAML expansion with template parameters (dry run, no queue)
azp check path/to/pipeline.yml --parameters env=staging
# Queue the run with multiple parameters, variables, and stage skips
azp run path/to/pipeline.yml --parameters env=staging,imageTag=latest --variables tag=v1,debug=true -s Deploy,Cleanup
# Wait for completion using the build ID from the previous step
azp wait 12345 -f
check and run require a clean working tree synced with upstream — commit
and push first.
# View run status as a tree (stages → jobs → tasks)
azp status 12345 -d 3
# Download logs for a specific task (logId shown in status -d 3 output)
azp logs 12345 42
# Cancel a running build
azp cancel 12345
| Flag | Purpose | Commands |
|---|---|---|
--parameters k=v[,k=v,...] | Template parameter overrides (comma-separated) | check, run |
--variables k=v[,k=v,...] | Pipeline variable overrides (comma-separated; must be settable at queue time) | run |
-s/--skip stage[,stage,...] | Stage names to skip (comma-separated) | run |
-d 1|2|3 | Tree depth: 1=stages, 2=+jobs (default), 3=+tasks | status |
-f | Exit with non-zero code on failure/cancellation | wait |
This repo includes a skill which shows AI coding assistants how to use azp to develop Azure Pipelines on your behalf.
With the azure-pipelines-tool skill, agents can check pipeline syntax, queue pipeline runs, investigate failing pipelines, and even wait for runs to complete and react accordingly.
azp install-skilldnx azp -y -- install-skill
The interactive installer lets you choose the target agent (GitHub Copilot, Claude Code, Gemini, or agent-agnostic) and whether to install locally or to your user directory.
/plugin marketplace add lbussell/AzurePipelinesTool
/plugin install azure-pipelines-tool@lbussell-azure-pipelines-tools
The plugin marketplace is also compatible with Claude Code.
See docs/development/ for build, test, and publishing instructions.