Skip to content

Robertjam954/multimodal_rag_application / .claude/skills/azure-deploy

azure-deploy

Flagged

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

FileKindSize
SKILL.mdskill md6.5 KB
references/auth-best-practices.mdmarkdown6.1 KB
references/global-rules.mdmarkdown1.2 KB
references/live-role-verification.mdmarkdown3.9 KB
references/pre-deploy-checklist.mdmarkdown18.4 KB
references/recipes/README.mdmarkdown431 B
references/recipes/azcli/README.mdmarkdown1.7 KB
references/recipes/azcli/errors.mdmarkdown492 B
references/recipes/azcli/verify.mdmarkdown2.0 KB
references/recipes/azd/README.mdmarkdown3.7 KB
references/recipes/azd/ef-migrations.mdmarkdown5.0 KB
references/recipes/azd/errors.mdmarkdown15.4 KB
references/recipes/azd/functions-deploy.mdmarkdown3.5 KB
references/recipes/azd/post-deployment.mdmarkdown4.2 KB
references/recipes/azd/scripts/apply-migrations.ps1script1.8 KB
references/recipes/azd/scripts/apply-migrations.shscript1.8 KB
references/recipes/azd/scripts/grant-and-migrate.ps1script4.2 KB
references/recipes/azd/scripts/grant-and-migrate.shscript4.3 KB
references/recipes/azd/sql-entra-auth.mdmarkdown2.5 KB
references/recipes/azd/sql-managed-identity.mdmarkdown7.4 KB
references/recipes/azd/verify.mdmarkdown4.9 KB
references/recipes/bicep/README.mdmarkdown2.4 KB
references/recipes/bicep/errors.mdmarkdown511 B
references/recipes/bicep/verify.mdmarkdown763 B
references/recipes/cicd/README.mdmarkdown1.2 KB
references/recipes/cicd/errors.mdmarkdown542 B
references/recipes/cicd/examples/azdo-azd.ymlconfig487 B
references/recipes/cicd/examples/azdo-multistage.ymlconfig831 B
references/recipes/cicd/examples/github-azd.ymlconfig782 B
references/recipes/cicd/examples/github-bicep.ymlconfig660 B
references/recipes/cicd/verify.mdmarkdown754 B
references/recipes/terraform/README.mdmarkdown3.2 KB
references/recipes/terraform/errors.mdmarkdown858 B
references/recipes/terraform/verify.mdmarkdown752 B
references/region-availability.mdmarkdown3.0 KB
references/sdk/azd-deployment.mdmarkdown792 B
references/sdk/azure-identity-dotnet.mdmarkdown941 B
references/sdk/azure-identity-java.mdmarkdown1.2 KB
references/sdk/azure-identity-py.mdmarkdown1.1 KB
references/sdk/azure-identity-ts.mdmarkdown1.1 KB
references/troubleshooting.mdmarkdown8.0 KB

references/recipes/azcli/README.md

View on GitHub
# Azure CLI Deploy Recipe

Deploy to Azure using Azure CLI.

## Prerequisites

- `az` CLI installed → Run `mcp_azure_mcp_extension_cli_install` with `cli-type: az` if needed
- `.azure/deployment-plan.md` exists with status `Validated`
- Bicep/ARM templates exist in `infra/`
- **Subscription and location confirmed** → See [Pre-Deploy Checklist](../../pre-deploy-checklist.md)

## Workflow

| Step | Task | Command |
|------|------|---------|
| 1 | **[Pre-deploy checklist](../../pre-deploy-checklist.md)** | Confirm subscription/location with user |
| 2 | Deploy infrastructure | `az deployment sub create` |
| 3 | Deploy application | Service-specific commands |
| 4 | Verify | `az resource list` |
| 5 | **Report** | Present deployed endpoint URLs to the user — see [Verification](verify.md) |

## Infrastructure Deployment

### Subscription-Level (Recommended)

```bash
az deployment sub create \
  --location eastus2 \
  --template-file ./infra/main.bicep \
  --parameters environmentName=dev
```

### Resource Group Level

```bash
az group create --name rg-myapp-dev --location eastus2

az deployment group create \
  --resource-group rg-myapp-dev \
  --template-file ./infra/main.bicep \
  --parameters environmentName=dev
```

## Application Deployment

### Container Apps

```bash
az containerapp update \
  --name <app-name> \
  --resource-group <rg-name> \
  --image <acr-name>.azurecr.io/myapp:latest
```

### App Service

```bash
az webapp deploy \
  --name <app-name> \
  --resource-group <rg-name> \
  --src-path ./publish.zip
```

### Azure Functions

```bash
func azure functionapp publish <function-app-name>
```

## References

- [Verification steps](./verify.md)
- [Error handling](./errors.md)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall