一键导入
Complete Azure DevOps automation - boards, repos, pipelines, artifacts
npx skills add https://github.com/rysweet/azure-tenant-grapher --skill azure-devops复制此命令并粘贴到 Claude Code 中以安装该技能
Complete Azure DevOps automation - boards, repos, pipelines, artifacts
npx skills add https://github.com/rysweet/azure-tenant-grapher --skill azure-devops复制此命令并粘贴到 Claude Code 中以安装该技能
Generates agentic outside-in tests using gadugi-agentic-test framework for CLI, TUI, Web, and Electron apps. Use when you need behavior-driven tests that verify external interfaces without internal implementation knowledge. Creates YAML test scenarios that AI agents execute, observe, and validate against expected outcomes. Supports progressive complexity from simple smoke tests to advanced multi-step workflows.
Comprehensive knowledge of Claude Agent SDK architecture, tools, hooks, skills, and production patterns. Auto-activates for agent building, SDK integration, tool design, and MCP server tasks.
Expert backlog manager that prioritizes work using multi-criteria scoring, analyzes dependencies, and recommends optimal next tasks. Activates when managing backlogs, prioritizing work, adding items, or analyzing what to work on next.
Auto-generates code flow diagrams from Python module analysis. Detects when architecture diagrams become stale (code changed, diagram didn't). Use when: creating new modules, reviewing PRs for architecture impact, or checking diagram freshness. Generates mermaid diagrams showing imports, dependencies, and module relationships.
Proactive context window management via token monitoring, intelligent extraction, and selective rehydration. Features predictive budget monitoring, context health indicators, and priority-based retention. Use when approaching token limits or needing to preserve essential context. Complements /transcripts and PreCompact hook with proactive optimization.
Development workflow for features, bugs, refactoring. Auto-activates for multi-file implementations.
| name | azure-devops |
| description | Complete Azure DevOps automation - boards, repos, pipelines, artifacts |
| version | 2.0.0 |
| type | skill |
| auto_activate_keywords | ["azure devops","work item","boards","wiql","ado","ado boards","devops work item","azure repos","pull request","azure pipelines","azure artifacts"] |
| tools_required | [".claude/scenarios/az-devops-tools/auth_check.py",".claude/scenarios/az-devops-tools/create_work_item.py",".claude/scenarios/az-devops-tools/update_work_item.py",".claude/scenarios/az-devops-tools/delete_work_item.py",".claude/scenarios/az-devops-tools/get_work_item.py",".claude/scenarios/az-devops-tools/list_work_items.py",".claude/scenarios/az-devops-tools/link_parent.py",".claude/scenarios/az-devops-tools/query_wiql.py",".claude/scenarios/az-devops-tools/format_html.py",".claude/scenarios/az-devops-tools/list_types.py",".claude/scenarios/az-devops-tools/list_repos.py",".claude/scenarios/az-devops-tools/create_pr.py"] |
| references | [{"name":"Azure DevOps CLI Documentation","url":"https://learn.microsoft.com/en-us/cli/azure/devops"},{"name":"az boards work-item Commands","url":"https://learn.microsoft.com/en-us/cli/azure/boards/work-item"},{"name":"Work Items REST API","url":"https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/work-items"},{"name":"WIQL Syntax Reference","url":"https://learn.microsoft.com/en-us/azure/devops/boards/queries/wiql-syntax"},{"name":"Work Item Fields","url":"https://learn.microsoft.com/en-us/azure/devops/boards/work-items/work-item-fields"},{"name":"Link Types Reference","url":"https://learn.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference"}] |
| supporting_docs | ["authentication.md","work-items.md","queries.md","html-formatting.md","repos.md","pipelines.md","artifacts.md","HOW_TO_CREATE_YOUR_OWN.md"] |
Complete Azure DevOps integration covering boards, repositories, pipelines, and artifacts.
Auto-activates when: User mentions Azure DevOps, ADO, work items, boards, repos, pipelines, artifacts, or Azure DevOps URLs.
This skill provides comprehensive guidance for Azure DevOps automation through purpose-built Python CLI tools that handle:
ALWAYS start by checking authentication:
python .claude/scenarios/az-devops-tools/auth_check.py --auto-fix
This verifies Azure CLI is installed, you're logged in, org/project are configured, and you have access.
See: [@authentication.md]
python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "User Story" \
--title "Implement feature" \
--description @story.md
python .claude/scenarios/az-devops-tools/list_work_items.py --query mine
python .claude/scenarios/az-devops-tools/create_pr.py \
--source feature/branch \
--target main \
--title "Add feature"
For detailed guidance on specific operations, see:
| Tool | Purpose | When to Use |
|---|---|---|
auth_check.py | Verify authentication | Before any operations |
create_work_item.py | Create work items | Add User Stories, Tasks, Bugs, etc. |
update_work_item.py | Update work items | Change state, assignee, fields |
delete_work_item.py | Delete work items | Remove work items (with confirmation) |
get_work_item.py | Get work item details | View complete work item info |
list_work_items.py | Query work items | Find, filter, and list work items |
link_parent.py | Link parent-child | Create Epic → Feature → Story hierarchies |
query_wiql.py | Execute WIQL queries | Complex filtering with WIQL |
format_html.py | Convert to HTML | Format rich descriptions |
list_types.py | Discover types/fields | Explore available options |
list_repos.py | List repositories | View all repositories in project |
create_pr.py | Create pull request | Submit code for review |
# Create parent work item
python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "Epic" \
--title "Q1 Planning Initiative" \
--description @epic_desc.md
# Output: Created work item #12345
# Create child and link to parent
python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "Feature" \
--title "Authentication System" \
--description @feature_desc.md \
--parent-id 12345
# Output: Created work item #12346 and linked to parent #12345
# Find your active work items
python .claude/scenarios/az-devops-tools/list_work_items.py \
--query mine \
--format ids-only
# Update work item state
python .claude/scenarios/az-devops-tools/update_work_item.py \
--id 12345 \
--state "Active" \
--comment "Starting work on this"
# List repositories
python .claude/scenarios/az-devops-tools/list_repos.py
# Create pull request
python .claude/scenarios/az-devops-tools/create_pr.py \
--source feature/auth \
--target main \
--title "Add authentication" \
--description @pr_desc.md \
--reviewers "user1@domain.com,user2@domain.com" \
--work-items "12345,12346"
# List all work item types in your project
python .claude/scenarios/az-devops-tools/list_types.py
# Show fields for specific type
python .claude/scenarios/az-devops-tools/list_types.py \
--type "User Story" \
--fields
Azure DevOps work item descriptions use HTML, not Markdown or plain text.
The tools handle this automatically:
create_work_item.py converts markdown to HTML by default--no-html to disable conversionformat_html.py directly for custom formattingSee: [@html-formatting.md]
You cannot specify a parent during work item creation via CLI (Azure limitation).
The tools provide two approaches:
Option A: Use --parent-id flag (recommended):
python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "Task" \
--title "My Task" \
--parent-id 12345
Option B: Link separately:
# Step 1: Create
TASK_ID=$(python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "Task" \
--title "My Task" \
--json | jq -r '.id')
# Step 2: Link
python .claude/scenarios/az-devops-tools/link_parent.py \
--child $TASK_ID \
--parent 12345
ProjectName\TeamName\SubArealist_types.py to discover what's available in your project| Error | Tool to Use | Example |
|---|---|---|
| Authentication failed | auth_check.py --auto-fix | Auto-login and configure |
| Invalid work item type | list_types.py | See available types |
| Field validation error | list_types.py --type "Type" --fields | See valid fields |
| Parent link failed | Check IDs exist, verify hierarchy rules | Epic → Feature → Story → Task |
| Branch does not exist | Verify with git branch -a | Push branch first |
All tools are in ~/.amplihack/.claude/scenarios/az-devops-tools/:
tests/ directorySee: Tool README
These tools follow amplihack principles:
# Setup (first time)
python .claude/scenarios/az-devops-tools/auth_check.py --auto-fix
# Create work item
python .claude/scenarios/az-devops-tools/create_work_item.py \
--type "User Story" \
--title "Title" \
--description @desc.md
# Update work item
python .claude/scenarios/az-devops-tools/update_work_item.py \
--id 12345 \
--state "Active"
# Query work items
python .claude/scenarios/az-devops-tools/list_work_items.py --query mine
# Create pull request
python .claude/scenarios/az-devops-tools/create_pr.py \
--source feature/branch \
--target main \
--title "Add feature"
# Discover types
python .claude/scenarios/az-devops-tools/list_types.py