القائمة
Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | az-devops-cli |
| description | Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI. |
Manage Azure DevOps resources using the Azure CLI with the Azure DevOps extension.
# Install Azure CLI
brew install azure-cli # macOS
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash # Linux
# Install Azure DevOps extension
az extension add --name azure-devops
# Login with PAT token
az devops login --organization https://dev.azure.com/{org} --token YOUR_PAT_TOKEN
# Set default organization and project (avoids repeating --org/--project)
# Note: Legacy URL https://{org}.visualstudio.com should be replaced with https://dev.azure.com/{org}
az devops configure --defaults organization=https://dev.azure.com/{org} project={project}
# List current configuration
az devops configure --list
az devops # Main DevOps commands
├── admin # Administration (banner)
├── extension # Extension management
├── project # Team projects
├── security # Security operations
│ ├── group # Security groups
│ └── permission # Security permissions
├── service-endpoint # Service connections
├── team # Teams
├── user # Users
├── wiki # Wikis
├── configure # Set defaults
├── invoke # Invoke REST API
├── login # Authenticate
└── logout # Clear credentials
az pipelines # Azure Pipelines
├── agent # Agents
├── build # Builds
├── folder # Pipeline folders
├── pool # Agent pools
├── queue # Agent queues
├── release # Releases
├── runs # Pipeline runs
├── variable # Pipeline variables
└── variable-group # Variable groups
az boards # Azure Boards
├── area # Area paths
├── iteration # Iterations
└── work-item # Work items
az repos # Azure Repos
├── import # Git imports
├── policy # Branch policies
├── pr # Pull requests
└── ref # Git references
az artifacts # Azure Artifacts
└── universal # Universal Packages
Read the relevant reference file based on the user's task. Each file contains complete command syntax and examples for its domain.
| File | When to read | Covers |
|---|---|---|
references/repos-and-prs.md | Repos, branches, pull requests, branch policies | Repositories, Import, PRs (create/list/vote/reviewers/policies), Git refs, Branch policies |
references/pipelines-and-builds.md | Pipelines, builds, releases, artifacts | Pipelines CRUD, runs, builds, releases, artifacts download/upload |
references/boards-and-iterations.md | Work items, sprints, area paths | Work items (WIQL/create/update/relations), Area paths, Iterations, Team iterations |
references/variables-and-agents.md | Pipeline variables, agent pools | Pipeline variables, Variable groups, Pipeline folders, Agent pools/queues |
references/org-and-security.md | Projects, teams, users, permissions, wikis | Projects, Extensions, Teams, Users, Security groups/permissions, Service endpoints, Wikis, Admin |
references/advanced-usage.md | Output formatting, JMESPath queries | Output formats, JMESPath queries (basic + advanced), Global args, Common params, Git aliases |
references/workflows-and-patterns.md | Automation scripts, best practices, error handling | Common workflows, Best practices, Error handling, Scripting patterns, Real-world examples |
Autonomously implement a specification produced by the specify skill. Reads the spec document, builds a task queue in the session database, implements tasks in parallel where dependencies allow, runs deterministic checks, spawns adversarial verification (different model), and iterates until all evaluation criteria pass or convergence is reached. Use when the user has a spec document (from the specify skill or a similar structured spec) and wants it implemented with guaranteed quality verification. Trigger phrases: "implement this spec", "build this", "execute the spec", "implement-spec", "start implementation", "make it happen", or when the user points to a ./specs/*.md file and asks to build it. Also use when the user has just finished using specify and says "now build it", "go", or "implement".
Guide the user through a structured specification process: define the goal, specify exactly what to build (and what NOT to build), and establish measurable evaluation criteria — all before implementation begins. Produces a living spec document. Use when the user has a goal or feature idea and wants to define the spec, says "specify this", "what's the spec", "define the specification", "how do I achieve this goal", "break this down", "what do I need to build", "write a spec", "define requirements", wants to create a specification with verification criteria, or has just finished using the-goal and wants to turn the goal into a precise, implementable specification. Also use when the user wants to define evaluation criteria before coding, or mentions "adversarial verification", "quality criteria", or "acceptance criteria".
Author, validate, and debug GitHub Copilot CLI extensions that add tools, commands, hooks, or session-event behavior. Use when creating or reviewing a Copilot CLI extension, wiring `joinSession`, deciding between project, user, or session scope, troubleshooting extension loading, or adding a custom Copilot CLI tool or slash command. Also use when the user wants a custom Copilot CLI extension scaffold or asks how extensions work.
Interview the user step-by-step to gather every detail needed to build a Microsoft 365 Copilot Cowork plugin package (manifest.json + skills + optional MCP connectors), then produce a complete, self-contained build prompt the user can review or hand off for execution. Use when the user asks to "create a cowork plugin", "build a copilot plugin", "make a M365 copilot agent package", "package my skills as a plugin", "create a copilot agent with MCP", "build a plugin for copilot cowork", or "wizard me through a cowork plugin". Do NOT use for: creating a single personal skill (use the `skills` skill instead), installing an existing plugin, troubleshooting plugin uploads that already exist, or general M365 admin questions.
Extract and clarify the real goal behind a feature, change, or idea through a focused interview. Inspired by Goldratt's *The Goal*. Use this skill whenever the user has a vague idea, a new feature request, or a change they want to make but the underlying goal is unclear, implicit, or too broad. Also use when the user says things like "I want to build X" without articulating why, or when scope creep is a risk and the real constraint needs to be identified first. This skill does not plan or solve — it only finds the goal.
Interview the developer about their workflow goals and produce a valid Playbook YAML file saved to ./playbooks/<name>.yml. A Playbook is a machine-executable workflow graph: Phases (logical groupings) containing Tasks (atomic executable units with inputs, outputs, dependencies, and success criteria). Trigger this skill when the user wants to design, create, edit, or author a repeatable multi-step agentic workflow. Covers the full interview → validate → save flow, including updating existing playbooks.