azure-developer-cli

by github40k

Design, create, review, migrate, or troubleshoot Azure Developer CLI (azd) projects using current Microsoft guidance. Use for azd, azure.yaml, AZD templates, Bicep or Terraform under infra, AZD enviro

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add github/awesome-copilot --skill azure-developer-cli -a cursor -y

Download skill skills/azure-developer-cli/SKILL.md on GitHub

Related skills

View all

name: azure-developer-cli description: 'Design, create, review, migrate, or troubleshoot Azure Developer CLI (azd) projects using current Microsoft guidance. Use for azd, azure.yaml, AZD templates, Bicep or Terraform under infra, AZD environments and secrets, hooks, deployment workflows, and azd-managed CI/CD.' license: MIT

Azure Developer CLI best practices

Use this skill to produce maintainable, secure, environment-aware azd projects. Prefer repository conventions when they are already coherent, and make the smallest complete change that improves the project.

Start with repository discovery

Before editing:

Find azure.yaml, the configured infra.path, source projects, deployment scripts, .gitignore, and pipeline definitions.
Read azure.yaml before inferring services or the IaC provider.
Identify whether the task is to create, migrate, review, deploy, or troubleshoot.
Identify the active environment only when an environment-specific operation is required.
Read the relevant reference:
- Repository layout or azure.yaml: references/project-structure.md
- Bicep, Terraform, parameters, outputs, or environments: references/iac-and-environments.md

Concern	Preferred default
Project manifest	One `azure.yaml` at the repository root
Application code	`src/<service-name>` per independently deployable service
Infrastructure	`infra` with a thin entry point and reusable modules
IaC provider	Bicep unless the repository or user chooses Terraform
Deployment environments	Separate named environments for dev, test, staging, and production
Local AZD state	`.azure/<environment-name>` and excluded from source control
Shared environment state	AZD remote environments backed by Azure Blob Storage
Secrets	Managed identity/RBAC first, then Key Vault references
Automation scripts	Short, idempotent scripts under `scripts/azd`
CI authentication	Workload identity federation/OIDC where supported
Routine development	`azd up` for simple workflows; separate phases for controlled workflows

azure-developer-cli

Install

Related skills

Azure Developer CLI best practices

Start with repository discovery

Apply safety guardrails

Use these defaults

Implementation workflow

1. Model the application

2. Model infrastructure

3. Model environments

4. Add hooks only for lifecycle gaps

5. Build CI/CD deliberately

Validate before finishing

Report the result