Loading...
Loading...
Found 31 Skills
Adds CI/CD to a .NET project. GitHub Actions vs Azure DevOps detection, workflow templates.
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
Expert knowledge for Chaos Studio development including troubleshooting, limits & quotas, security, configuration, and integrations & coding patterns. Use when defining ARM/Bicep experiments, deploying Chaos Agents, using CLI/REST, or integrating with Azure Monitor, and other Chaos Studio related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Site Recovery (use azure-site-recovery).
Create well-formatted conventional commits in a repository hosted on Azure DevOps (ADO / Azure Repos). Use this whenever the user asks to commit changes and the project is on Azure DevOps — dev.azure.com, visualstudio.com, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`. Automatically appends `AB#<id>` work-item trailers when the branch name or staged changes reference one, and attributes AI-assisted authorship.
Publishes .NET artifacts from Azure DevOps. NuGet push, containers to ACR, pipeline artifacts.
Generates the Data Engineering team weekly/sprint status report from Azure DevOps. Organized by Epic, with objectives, on/off track status, risks, completed and planned items per area, clickable ADO links, and unplanned items flagged. Use when the user asks for a Data Engineering sprint report, weekly report, current sprint status, activities report, or sprint summary.
Use when extracting requirements from Azure DevOps work items using dxs devops commands: fetching work items, reviewing relations, downloading attachments, compiling raw requirements. This is a utility skill — it extracts and structures work item content but does not build reports, datasources, or other artifacts.