devops-azurelisted

Read and create Azure DevOps work items and PRs via the az CLI (devops extension) for the org/projects in AZURE_DEVOPS_ORG/AZURE_DEVOPS_PROJECTS. Use for one-off Azure Boards/Repos operations outside the code pipeline: viewing or creating work items, viewing PRs, commenting, updating state, linking commits. Also provides batch write mode (step 8), turning a reviewed /backlog tree into work items in one pass -- whole-tree preview, one confirmation, per-item reporting, ids written back. Trigger this when someone says: check my work items, list open PRs in Azure DevOps, create a work item, comment on PR #N, close this work item, connect to azure devops, create the work items from this backlog, push this backlog tree into ADO. Do NOT use for GitHub PRs/issues -- that's skills/devops-github. Do NOT use for a full review or implementation pipeline -- use /review-pr or /implement. Do NOT use to decompose a spec into a backlog -- that is /backlog; batch mode consumes its tree and never produces one.
chuckplayer/claude-agent-pack · ★ 6 · DevOps & Infrastructure · score 76

Install: claude install-skill chuckplayer/claude-agent-pack

# Azure DevOps (az CLI) Read and write Azure DevOps work items and PRs by shelling out to the `az` CLI with the `devops` extension — no MCP server required. Handles first-time setup, operation-aware targeting (an ID-scoped lookup needs only the org; a project-scoped query, list, or write needs a resolved project), runtime field-schema discovery, and safe write operations for the org/projects configured via environment variables. ## 1. Verify setup Check, in order: 1. **`az` CLI installed?** Run `az --version`. If missing, stop and direct the user to install it (https://learn.microsoft.com/cli/azure/install-azure-cli). 2. **`devops` extension installed?** Run `az extension show --name azure-devops`. If missing, install it with `az extension add --name azure-devops` (ask before installing). 3. **Authenticated?** Run `az account show`. If not logged in, walk the user through `az login` interactively. Once org/project targeting is resolved (steps 2–3 below), optionally set defaults for convenience with `az devops configure --defaults organization=<org> project=<project>` — do not do this before targeting is confirmed. 4. **Env vars set?** Check `AZURE_DEVOPS_ORG` (single value) and `AZURE_DEVOPS_PROJECTS` (comma-delimited list, e.g. `AZURE_DEVOPS_PROJECTS=<project-a>,<project-b>`). If unset, ask the user for the org and project(s) they want to work with — do not hardcode any org/project name into this file. Report each check's result clearly before proceeding. ## 1a. Persis