Operate Azure DevOps through native az CLI devops, boards, repos, pipelines, and artifacts commands.
npx skills add https://github.com/leonardoacosta/agents --skill az-ado-leonardoacosta
Please help me install this Agent Skill. Skill: az-ado Source: https://github.com/leonardoacosta/agents/tree/main/skills/az-ado Command: npx skills add https://github.com/leonardoacosta/agents --skill az-ado-leonardoacosta
az ado command, syntax varies across five command roots, empty output is easily misread as an empty result, and unguarded writes can misassign work items or queue unintended deployments. This Skill provides verified command routing, response validation rules, and authorization guardrails for safe ADO operations. ## Core Features & Use Cases - Command routing and discovery: Maps tasks to the correct root (az devops, az boards, az repos, az pipelines, az artifacts) with 269 captured help pages as navigation references, while requiring live -h verification before execution. - Board and identity workflows: Covers WIQL queries (including the @project macro limitation in extension 1.0.8), work-item hierarchy mapping, assignee identity resolution, and relation changes with cycle and conflict detection. - Response and effects contract: Enforces JSON output parsing, pagination checks, write read-backs, and explicit authority requirements for deletions, permission changes, and pipeline queueing. - Use Case: You need to inventory 800+ work items in a project and propose a re-parenting plan. The Skill guides you to partition the WIQL query by ID bounds, verify identities with az devops user show, preview exact relation changes, and read back every write. ## Quick Start Ask the agent to list all work items in your Azure DevOps project using the az-ado skill and verify the results with a read-back query.High-intent search queries and answers about installing and using this skill.
Use `az boards query --wiql` with a WIQL statement, or pass a saved query via `--id` or `--path`. Note that extension 1.0.8 does not expand the `@project` macro in WIQL, so use an explicit escaped project-name literal, and partition large inventories by ID bounds since detail retrieval caps at 1,000 items.
The azure-devops extension exposes `az devops` plus the related roots `az boards`, `az repos`, `az pipelines`, and `az artifacts`; `az ado` is not native syntax. Run `az devops -h` and follow the advertised subgroups to discover the correct command path.
First resolve the person to an exact identity with `az devops user show --user <email-or-id>`, then run `az boards work-item update --id <id> --assigned-to <identity>`. Be aware that `az devops user list` excludes users added through AAD groups, so a missing entry is not proof the identity does not exist.
Empty stdout can mean the WIQL matched nothing, the `@project` macro failed silently, or the response was malformed. Validate with `--output json`, compare against a harmless version or help response, and retry with an explicit project-name literal before concluding there are no matches.
Yes, use `az devops invoke` with explicit `--area`, `--resource`, `--http-method`, and a pinned `--api-version` rather than the default 5.0. Classify operations by documented endpoint semantics since some read-only queries use POST, and treat writes as requiring an approved plan.
Classify the operation's effects first: creates, updates, relation changes, wiki edits, uploads, and pipeline queues are all writes, and queueing can trigger deployments. Require explicit authority for deletions, permission changes, and PR completion, never place PATs or tokens in argv or files, and read back every write to confirm the result.
mattmacleod16-svgAutomate Azure DevOps resource management via the Azure CLI extension.
zeuikliGenerate sprint plans, RICE/MoSCoW prioritization, status reports, retrospectives, and risk matrices.
shellicarCreate, query, update, and migrate Azure DevOps work items via az boards.
tfsugjpAutomate Azure DevOps resource management via the Azure CLI extension.