azure-boards
Work with Azure DevOps Product Backlog Items using az boards CLI
What this skill does
# Azure Boards Skill
Use the Azure CLI (`az boards`) to interact with Azure DevOps work items.
## Prerequisites
Ensure Azure CLI is authenticated:
```bash
az login
az devops configure --defaults organization=https://dev.azure.com/{org} project={project}
```
## Fetching Work Items
### Single Work Item
```bash
az boards work-item show --id {id} --output yaml
```
### Field Mapping
| Azure DevOps Field | YAML Path | Notes |
|--------------------|-----------|-------|
| Title | `fields.System.Title` | Plain text |
| Description | `fields.System.Description` | HTML-formatted, strip tags |
| Acceptance Criteria | `fields.Microsoft.VSTS.Common.AcceptanceCriteria` | HTML-formatted |
| State | `fields.System.State` | New, Active, Resolved, Closed |
| Assigned To | `fields.System.AssignedTo` | User object |
| Iteration Path | `fields.System.IterationPath` | Sprint path |
| Priority | `fields.Microsoft.VSTS.Common.Priority` | 1-4 |
### HTML Parsing Notes
- Description and Acceptance Criteria are HTML-formatted
- Strip `<div>`, `<p>`, `<ul>`, `<li>`, `<code>` tags before processing
- Look for embedded sections as `<h3>` or `<b>` headers:
- "Files to modify" -> extract file paths
- "Scope" or "Architecture" -> extract context
- Numbered/bulleted lists -> extract changes
## Updating Work Items
### Update Fields
```bash
az boards work-item update --id {id} \
--fields \
"System.Description={description_html}" \
"Microsoft.VSTS.Common.AcceptanceCriteria={criteria_markdown}"
```
### Field Formats
- `System.Description`: HTML with `<h3>`, `<p>`, `<ul>`, `<ol>`, `<li>`, `<code>` tags
- `Microsoft.VSTS.Common.AcceptanceCriteria`: Markdown bullet list (no checkboxes)
### Example Update
```bash
az boards work-item update --id 12345 \
--fields \
"System.Description=<h3>Context</h3><p>Switch to internal ingress.</p><h3>Files</h3><ul><li><code>container-app.bicep</code></li></ul>" \
"Microsoft.VSTS.Common.AcceptanceCriteria=- Direct URL returns 403\n- Front Door URL returns 200"
```
## WIQL Queries
### My Active Work Items
```sql
SELECT [System.Id], [System.Title], [System.State], [System.WorkItemType], [Microsoft.VSTS.Common.Priority]
FROM WorkItems
WHERE [System.AssignedTo] = @Me
AND [System.WorkItemType] IN ('Product Backlog Item', 'Bug')
AND [System.State] NOT IN ('Closed', 'Removed', 'Resolved')
ORDER BY [Microsoft.VSTS.Common.Priority] ASC, [System.WorkItemType] ASC
```
### Sprint Work Items
```sql
SELECT [System.Id], [System.Title], [System.State]
FROM WorkItems
WHERE [System.AssignedTo] = @Me
AND [System.IterationPath] = '{iteration_path}'
AND [System.State] NOT IN ('Closed', 'Removed')
```
### Execute WIQL
```bash
az boards query --wiql "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.AssignedTo] = @Me" --output table
```
## Creating Tasks Under a PBI
```bash
az boards work-item create \
--type Task \
--title "Task title" \
--description "Task description" \
--fields "System.Parent={pbi_id}"
```
## Common Operations
### List Work Item Types
```bash
az boards work-item type list --output table
```
### Show Work Item Relations
```bash
az boards work-item show --id {id} --expand relations
```
### Add Comment
```bash
az boards work-item update --id {id} --discussion "Comment text"
```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.