Robertjam954/multimodal_rag_application / .claude/skills/azure-deploy
azure-deploy
FlaggedExecute 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.
references/recipes/azd/scripts/apply-migrations.ps1
View on GitHub# Apply EF Core database migrations to Azure SQL using Managed Identity authentication.
#
# USAGE: Copy this file to scripts/apply-migrations.ps1 in your project root and add
# a postprovision hook in azure.yaml:
#
# hooks:
# postprovision:
# posix:
# shell: sh
# run: ./scripts/apply-migrations.sh
# windows:
# shell: pwsh
# run: ./scripts/apply-migrations.ps1
#
# ENVIRONMENT VARIABLES (sourced from azd env):
# SQL_SERVER - SQL server name (without .database.windows.net)
# SQL_DATABASE - Database name
#
# PREREQUISITES:
# - dotnet-ef tool (installed automatically if missing)
# - A valid managed identity or Entra-authenticated session
#
# CONFIGURATION:
# Set $AppProjectPath below to the path of your application project (.csproj directory)
$ErrorActionPreference = 'Stop'
$AppProjectPath = "src/api" # Adjust to your project directory
# Load azd environment variables
azd env get-values | ForEach-Object {
$name, $value = $_.Split('=', 2)
Set-Item "env:$name" $value.Trim('"')
}
# Install dotnet-ef if not already installed (no-op when already present)
$globalTools = dotnet tool list --global 2>$null
if ($LASTEXITCODE -ne 0) {
throw "Failed to list globally installed .NET tools."
}
if (-not ($globalTools | Select-String -Pattern '^\s*dotnet-ef\s')) {
dotnet tool install --global dotnet-ef
if ($LASTEXITCODE -ne 0) {
throw "Failed to install dotnet-ef."
}
}
$env:PATH += ";$env:USERPROFILE\.dotnet\tools"
$ConnectionString = "Server=tcp:$($env:SQL_SERVER).database.windows.net,1433;Database=$($env:SQL_DATABASE);Authentication=Active Directory Default;Encrypt=True;"
Write-Host "Applying EF Core migrations..."
Set-Location $AppProjectPath
dotnet ef database update --connection $ConnectionString
Write-Host "Migrations applied successfully."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |