azure-cli
When users share links (such as visualstudio.com or dev.azure.com) and/or mention Azure DevOps, use the Azure DevOps CLI to interact with work items, pull requests (PRs), repositories, and more.
What this skill does
# Azure DevOps CLI
You have access to an already signed in version of the Azure CLI with devops access. When users share Azure DevOps links or mention Azure DevOps resources, infer the appropriate action from context before running commands.
## Parsing Azure DevOps URLs
Extract parameters from common URL patterns:
- `https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{prId}`
- `https://{org}.visualstudio.com/{project}/_git/{repo}/pullrequest/{prId}`
- `https://dev.azure.com/{org}/{project}/_workitems/edit/{workItemId}`
## Pull Requests
**Important**: Most `az repos pr` commands require the `--org {orgUrl}` parameter to identify the Azure DevOps organization. The exception is `az repos pr checkout`, which operates on the local git repository and does NOT require `--org`.
Infer user intent from context when they share a PR link:
| Context | Likely Action |
| -------------------------------- | ----------------------------------------- |
| "review", "comments", "feedback" | Get comment threads |
| "what's this PR", "show me" | Show PR details |
| "check out", "work on this" | Checkout PR branch |
| "approve", "complete", "merge" | Update PR status |
| No clear intent | Show PR summary first, ask what they need |
### Show PR Details
```shell
az repos pr show --id {prId} --org {orgUrl}
```
### Checkout PR Branch
**Note**: This command does NOT require `--org` because it operates on the local git repository context.
```shell
az repos pr checkout --id {prId}
```
### Get PR File Changes
Use `az devops invoke` to get the list of files and diffs:
```shell
az devops invoke --area git --resource pullRequests --route-parameters repositoryId={repo} pullRequestId={prId} --org {orgUrl} --api-version 7.1
```
### Get PR Comment Threads
The CLI lacks a first-class command for threads; use `az devops invoke`:
```shell
az devops invoke --area git --resource pullRequestThreads --route-parameters project={project} repositoryId={repository} pullRequestId={prId} --org {orgUrl} --api-version 7.1
```
Filter to active/unresolved threads:
```shell
... | jq '.value[] | select(.status == "active")'
```
### Create PR Comment Thread
General comment (not attached to a file):
```shell
az devops invoke --area git --resource pullRequestThreads \
--route-parameters project={project} repositoryId={repo} pullRequestId={pr} \
--http-method POST --api-version 7.1-preview --org {orgUrl} \
--body '{
"comments": [{"parentCommentId": 0, "content": "Your comment", "commentType": "text"}],
"status": "active"
}'
```
File-specific comment (attached to specific lines):
```shell
az devops invoke --area git --resource pullRequestThreads \
--route-parameters project={project} repositoryId={repo} pullRequestId={pr} \
--http-method POST --api-version 7.1-preview --org {orgUrl} \
--body '{
"comments": [{"parentCommentId": 0, "content": "Your comment", "commentType": "text"}],
"status": "active",
"threadContext": {
"filePath": "/path/to/file.js",
"rightFileStart": {"line": 10, "offset": 0},
"rightFileEnd": {"line": 15, "offset": 0}
}
}'
```
### Vote on a PR
```shell
# approve, approve-with-suggestions, wait-for-author, reject, reset
az repos pr set-vote --id {prId} --vote approve --org {orgUrl}
```
### Update PR Status
```shell
az repos pr update --id {prId} --status completed --org {orgUrl} # or: abandoned
```
### List Linked Work Items
```shell
az repos pr work-item list --id {prId} --org {orgUrl}
```
### Manage Reviewers
```shell
az repos pr reviewer add --id {prId} --reviewers {email} --org {orgUrl}
az repos pr reviewer list --id {prId} --org {orgUrl}
```
## Work Items
### Show Work Item Details
```shell
az boards work-item show --id {workItemId} --org {orgUrl}
```
### Update Work Item
```shell
az boards work-item update --id {workItemId} --state "Active" --org {orgUrl}
az boards work-item update --id {workItemId} --assigned-to {email} --org {orgUrl}
```
### Create Work Item
```shell
az boards work-item create --title "Title" --type "Task" --project {project} --org {orgUrl}
```
### Query Work Items (WIQL)
```shell
az boards query --wiql "SELECT [System.Id] FROM workitems WHERE [System.AssignedTo] = @Me" --org {orgUrl}
```
### Manage Work Item Relations
```shell
az boards work-item relation add --id {workItemId} --relation-type "Parent" --target-id {targetId} --org {orgUrl}
```
## Using `az devops invoke` for REST APIs
When the CLI lacks a first-class command, use `invoke` to call any Azure DevOps REST API:
```shell
az devops invoke --area {area} --resource {resource} --route-parameters {key}={value} --org {orgUrl} --api-version 7.1
```
Common areas: `git`, `wit` (work item tracking), `core`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.