awesome-copilot-agents

The az containerapp command is used to manage Azure Container Apps. The CLI is organized into several functional subgroups. Use these subgroups to target specific management tasks such as authentication, environment configuration, ingress settings, or job management.

Key functional areas include:

• Core Management: _root, create, delete, list, show, update, patch, up.
• Networking & Connectivity: connection, connected-env, ingress, hostname, ssl.
• Runtime & Scaling: replica, revision, session, sessionpool, resiliency.
• Security & Identity: auth, identity, secret.
• Application Logic: dapr, function, java, job.
• Observability: logs, list-usages, debug.
• Infrastructure: env, registry, add-on, arc.

The az-cli skill is designed to help users manage Azure resources via the Azure CLI (az). It can be triggered when a user asks to create, configure, manage, deploy, or interact with Azure resources, or when they ask about Azure CLI command syntax and availability.

Prerequisites:

• The az-cli must be installed on the host system (Installation Guide).
• The CLI must be authenticated via az login.

# Ensure az-cli is installed and authenticated
az login

The az aro command group provides a reference for managing Azure Red Hat OpenShift (ARO) clusters via the Azure CLI. Use these commands to perform lifecycle operations such as creating, deleting, updating, and inspecting clusters, as well as managing credentials and versions.

# Create a cluster.
az aro create

# Delete a cluster.
az aro delete

# List clusters.
az aro list

# Get the details of a cluster.
az aro show

# Update a cluster.
az aro update

The az networkfabric CLI command group is used to manage various components of a Network Fabric infrastructure, including controllers, devices, networks, and security policies. Most resource types support standard CRUD operations (create, delete, list, show, update) and a wait command to pause execution until a specific condition is met.

# Example: List all Network Fabrics
az networkfabric fabric list

# Example: Show details of a specific Network Fabric
az networkfabric fabric show

The az devcenter admin command group is used for high-level administrative tasks within a Dev Center, such as managing catalogs, projects, network connections, and dev box definitions. These commands are typically used for infrastructure setup and governance rather than day-to-day developer workflows.

# Example: Create a new dev center
az devcenter admin devcenter create

# Example: List all dev centers in a resource group
az devcenter admin devcenter list

The azure-prices skill allows you to fetch and compare live Azure service pricing using the Azure Retail Prices API. It is designed to answer questions about Azure costs, rates, or comparisons across regions and services.

Requirements:

• Node.js must be installed.
• No Azure credentials are required as it uses the public Azure Retail Prices API.

Execution Rule: Always use the bundled npm scripts for price lookups. DO NOT call the Azure Retail Prices API directly; you must use the provided scripts to interface with the API.

The az container command group is used to manage Azure Container Instances (ACI) and container groups. It allows you to create, delete, start, stop, and inspect container groups, as well as execute commands within running containers.

# Example of common container management commands
az container create --resource-group myResourceGroup --name myContainerGroup --image mcr.microsoft.com/azuredocs/aci-helloworld
az container list --resource-group myResourceGroup
az container show --name myContainerGroup --resource-group myResourceGroup

Copilot Agents are used to enhance the GitHub Copilot experience by providing contextual details about your repository. By using customized instructions, prompts, agent skills, MCPs (Model Context Protocol), and custom agents, you can guide Copilot on:

• Team workflows
• Project-specific tools
• Coding styles
• Frameworks used
• Project-specific rules

For implementation details on how to customize GitHub Copilot in VS Code, refer to the VS Code documentation.