skills

Enforces approval guardrails for Azure operations. Unless an operation is pre-approved in a project allowlist, any command that deletes or modifies existing Azure resources or user accounts requires explicit user approval before execution. Activate whenever executing Azure operations via az CLI, azd, Azure PowerShell (Az module), Azure MCP tools, or Microsoft Graph — especially before any delete, update, set, remove, or identity-related command.

Validate NuGet package versions before adding or updating packages in .NET projects. Use when choosing a NuGet package version, checking package vulnerabilities, avoiding deprecated packages, auditing dotnet package list results, or requiring confirmation for packages not published in over one year.

Work with GitHub Advanced Security for Azure DevOps (GHAzDO): list and triage code/secret/dependency scanning alerts, dismiss (close) alerts, and associate alerts with work items. Use when the user asks about Advanced Security alerts, CodeQL findings, secret scanning, or dependency vulnerabilities in Azure Repos. REST-API-based — the Azure DevOps MCP Server has no Advanced Security tools.

Manage Azure Artifacts: list and create feeds, inspect package versions, promote packages between views, delete/unlist versions, and publish/download Universal Packages. Use when the user asks about Azure DevOps package feeds, NuGet/npm/Maven/Python/Universal packages, or feed views. REST/CLI-based — the Azure DevOps MCP Server has no Artifacts tools.

Manage Azure Boards work items: create, update fields, add comments, link items, and close them. Use when the user asks to create/update/comment on/close bugs, tasks, user stories, or other work items in Azure DevOps. Prefers Azure DevOps MCP Server tools and falls back to the REST API.

Shared foundation for all Azure DevOps skills: how to detect and configure the Azure DevOps MCP Server, and how to fall back to the REST API (Entra ID or PAT authentication) when MCP tools are unavailable. Read this before using any azure-devops-* skill.

Manage Azure Pipelines: create YAML pipeline definitions, queue runs, and monitor builds including stage control and log analysis. Use when the user asks to create, run, watch, or debug Azure DevOps pipelines or builds. Prefers Azure DevOps MCP Server tools and falls back to the REST API.

Work with Azure Repos pull requests: create PRs, review and vote, manage comment threads, resolve comments, and complete or abandon PRs. Use when the user asks to create, review, comment on, or merge pull requests in Azure DevOps. Prefers Azure DevOps MCP Server tools and falls back to the REST API.

End-to-end remediation workflow for GitHub Advanced Security alerts in Azure DevOps: triage open alerts, create tracking work items, drive a fix through branch and pull request, verify the re-scan closes the alert, and dismiss false positives with documented reasons. Use when the user asks to triage, remediate, or burn down Advanced Security findings.

Manage Azure Test Plans: create test plans, suites, and test cases, update test steps, and read test results from builds. Use when the user asks to create or organize test plans/suites/cases, generate test cases from work items, or check test results in Azure DevOps. Prefers Azure DevOps MCP Server tools and falls back to the REST API.

Work with Azure DevOps wikis: read, search, create, and update wiki pages, and publish generated content such as release notes or sprint reports. Use when the user asks to read or write Azure DevOps wiki pages. Prefers Azure DevOps MCP Server tools and falls back to the REST API.

Consolidates multiple open Dependabot pull requests in a GitHub (github.com or GitHub Enterprise) repository into a single PR backed by one English tracking issue, then iterates on reviewer/Copilot feedback until the PR is clean and mergeable. Use this whenever someone wants to merge/combine/consolidate/clean up a pile of Dependabot PRs, reduce dependency-bump noise, or says things like "dependabotのPRをまとめて" or "combine these dependency update PRs into one". Always drafts a plan and gets explicit confirmation before creating issues, opening PRs, or closing anything — these are hard-to-reverse, collaborator-visible actions.

Update Azure Verified Modules (AVM) to latest versions in Bicep files.

Guide for capturing application requirements and designing Azure Cosmos DB for NoSQL data models. Use when asked to model entities, define access patterns, choose partition keys, estimate scale, review denormalization tradeoffs, or produce `cosmosdb_requirements.md` and `cosmosdb_data_model.md` artifacts.

Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application.

Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.

Design Azure infrastructure using natural language, or analyze existing Azure resources to auto-generate architecture diagrams, refine them through conversation, and deploy with Bicep. When to use this skill: - "Create X on Azure", "Set up a RAG architecture" (new design) - "Analyze my current Azure infrastructure", "Draw a diagram for rg-xxx" (existing analysis) - "Foundry is slow", "I want to reduce costs", "Strengthen security" (natural language modification) - Azure resource deployment, Bicep template generation, IaC code generation - Microsoft Foundry, AI Search, OpenAI, Fabric, ADLS Gen2, Databricks, and all Azure services

Fetches real-time Azure retail pricing using the Azure Retail Prices API (prices.azure.com) and estimates Copilot Studio agent credit consumption. Use when the user asks about the cost of any Azure service, wants to compare SKU prices, needs pricing data for a cost estimate, mentions Azure pricing, Azure costs, Azure billing, or asks about Copilot Studio pricing, Copilot Credits, or agent usage estimation. Covers compute, storage, networking, databases, AI, Copilot Studio, and all other Azure service families.

Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.

Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project.

Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming.

Import existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM). Use when asked to reverse-engineer live Azure infrastructure, generate Infrastructure as Code from existing subscriptions/resource groups/resource IDs, map dependencies, derive exact import addresses from downloaded module source, prevent configuration drift, and produce AVM-based Terraform files ready for validation and planning across any Azure resource type.