Trim PR #1092 to AVM-focused changes

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jongio

plugin/skills/azure-deploy/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: azure-deploy
-description: "Deploy validated applications to Azure via azd, Bicep, or Terraform execution steps. WHEN: \"run azd up\", \"run azd deploy\", \"deploy to Azure\", \"bicep deploy\", \"terraform apply\", \"publish to Azure\", \"go live\"."
+description: "Deploy already-prepared applications to Azure by running azd up, azd deploy, or infrastructure provisioning commands. Supports Bicep and Terraform projects. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\", \"provision infrastructure\", \"push to production\", \"push to cloud\", \"go live\", \"ship it\", \"bicep deploy\", \"terraform apply\", \"publish to Azure\", \"launch on Azure\"."
 ---
 
 # Azure Deploy
@@ -9,7 +9,7 @@ description: "Deploy validated applications to Azure via azd, Bicep, or Terrafor
 >
 > **PREREQUISITE**: The **azure-validate** skill **MUST** be invoked and completed with status `Validated` BEFORE executing this skill.
 
-> **⚠️ STOP — PREREQUISITE CHECK REQUIRED**
+> **⛔ STOP — PREREQUISITE CHECK REQUIRED**
 > Before proceeding, verify BOTH prerequisites are met:
 >
 > 1. **azure-prepare** was invoked and completed → `.azure/plan.md` exists
@@ -19,7 +19,7 @@ description: "Deploy validated applications to Azure via azd, Bicep, or Terrafor
 > - No plan? → Invoke **azure-prepare** skill first
 > - Status not `Validated`? → Invoke **azure-validate** skill first
 >
-> **⚠️ DO NOT MANUALLY UPDATE THE PLAN STATUS**
+> **⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS**
 >
 > You are **FORBIDDEN** from changing the plan status to `Validated` yourself. Only the **azure-validate** skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.
 >
@@ -35,7 +35,7 @@ Activate this skill when user wants to:
 - Push updates to existing deployment
 - Run `azd up` or `az deployment`
 - Ship code to production
-- Deploy Azure serverless apps to the cloud
+- Deploy Azure Functions to the cloud
 - Deploy an application that already includes API Management (APIM) gateway infrastructure
 
 > **APIM / AI Gateway**: Use this skill to deploy applications whose APIM/AI gateway infrastructure was already created during **azure-prepare**. For creating or changing APIM resources, see [APIM deployment guide](https://learn.microsoft.com/azure/api-management/get-started-create-service-instance). For AI governance policies, invoke **azure-aigateway** skill.
@@ -45,7 +45,7 @@ Activate this skill when user wants to:
 1. Run after azure-prepare and azure-validate
 2. `.azure/plan.md` must exist with status `Validated`
 3. **Pre-deploy checklist required** — [Pre-Deploy Checklist](references/pre-deploy-checklist.md)
-4. ⚠️ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)
+4. ⛔ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)
 
 ---
 
@@ -57,11 +57,10 @@ Activate this skill when user wants to:
 | 2 | **Pre-Deploy Checklist** — MUST complete ALL steps | [Pre-Deploy Checklist](references/pre-deploy-checklist.md) |
 | 3 | **Load Recipe** — Based on `recipe.type` in `.azure/plan.md` | [recipes/README.md](references/recipes/README.md) |
 | 4 | **Execute Deploy** — Follow recipe steps | Recipe README |
-| 5 | **Post-Deploy** — Configure SQL managed identity and apply EF migrations if applicable | [Post-Deployment](references/recipes/azd/post-deployment.md) |
-| 6 | **Handle Errors** — See recipe's `errors.md` | — |
-| 7 | **Verify Success** — Confirm deployment completed and endpoints are accessible | [Verify](references/recipes/azd/verify.md) |
+| 5 | **Handle Errors** — See recipe's `errors.md` | — |
+| 6 | **Verify Success** — Confirm deployment completed and endpoints are accessible | — |
 
-> **⚠️ VALIDATION PROOF CHECK**
+> **⛔ VALIDATION PROOF CHECK**
 >
 > When checking the plan, verify the **Validation Proof** section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke **azure-validate** skill first.
 
@@ -80,5 +79,4 @@ Activate this skill when user wants to:
 
 ## References
 
-- [Troubleshooting](references/troubleshooting.md) - Common issues and solutions
-- [Post-Deployment Steps](references/recipes/azd/post-deployment.md) - SQL + EF Core setup
+- [Troubleshooting](references/troubleshooting.md) - Common issues and solutions

plugin/skills/azure-prepare/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: azure-prepare
-description: "Prepare applications for Azure deployment, except cross-cloud scenarios (use azure-cloud-migrate). Generates or updates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles. WHEN: \"prepare app for Azure\", \"build web app and host on Azure\", \"move on-premises application to Azure\", \"configure Azure hosting\", \"create Azure app\", \"add Azure service\", \"modernize app for Azure\", \"generate azure.yaml\", \"generate Bicep\", \"generate Terraform\", \"create Azure Functions app\"."
+description: "Default entry point for Azure application development EXCEPT cross-cloud migration — use azure-cloud-migrate instead. Analyzes your project and prepares it for Azure deployment by generating infrastructure code (Bicep/Terraform), azure.yaml, and Dockerfiles. WHEN: \"create an app\", \"build a web app\", \"create API\", \"create frontend\", \"create backend\", \"add a feature\", \"build a service\", \"develop a project\", \"modernize my code\", \"update my application\", \"add database\", \"add authentication\", \"add caching\", \"deploy to Azure\", \"host on Azure\", \"Azure with terraform\", \"Azure with azd\", \"generate azure.yaml\", \"generate Bicep\", \"generate Terraform\", \"create Azure Functions app\", \"create serverless HTTP API\", \"create function app\", \"create event-driven function\", \"create and deploy to Azure\", \"create Azure Functions and deploy\", \"create function app and deploy\"."
 ---
 
 # Azure Prepare
@@ -29,11 +29,11 @@ Activate this skill when user wants to:
 4. **Update plan progressively** — Mark steps complete as you go
 5. **Validate before deploy** — Invoke azure-validate before azure-deploy
 6. **Confirm Azure context** — Use `ask_user` for subscription and location per [Azure Context](references/azure-context.md)
-7. ⚠️ **Destructive actions require `ask_user`** — [Global Rules](references/global-rules.md)
+7. ⛔ **Destructive actions require `ask_user`** — [Global Rules](references/global-rules.md)
 
 ---
 
-## ⚠️ PLAN-FIRST WORKFLOW — MANDATORY
+## ⛔ PLAN-FIRST WORKFLOW — MANDATORY
 
 > **YOU MUST CREATE A PLAN BEFORE DOING ANY WORK**
 >
@@ -46,7 +46,7 @@ Activate this skill when user wants to:
 
 ---
 
-## ⚠️ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
+## ⛔ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
 
 **BEFORE starting Phase 1**, check if the user's prompt mentions a specialized technology that has a dedicated skill with tested templates. If matched, **invoke that skill FIRST** — then resume azure-prepare for validation and deployment.
 
@@ -69,7 +69,7 @@ Create `.azure/plan.md` by completing these steps. Do NOT generate any artifacts
 
 | # | Action | Reference |
 |---|--------|-----------|
-| 0 | **⚠️ Check Prompt for Specialized Tech** — If user mentions copilot SDK, Azure Functions, etc., invoke that skill first | [specialized-routing.md](references/specialized-routing.md) |
+| 0 | **⛔ Check Prompt for Specialized Tech** — If user mentions copilot SDK, Azure Functions, etc., invoke that skill first | [specialized-routing.md](references/specialized-routing.md) |
 | 1 | **Analyze Workspace** — Determine mode: NEW, MODIFY, or MODERNIZE | [analyze.md](references/analyze.md) |
 | 2 | **Gather Requirements** — Classification, scale, budget | [requirements.md](references/requirements.md) |
 | 3 | **Scan Codebase** — Identify components, technologies, dependencies | [scan.md](references/scan.md) |
@@ -81,7 +81,7 @@ Create `.azure/plan.md` by completing these steps. Do NOT generate any artifacts
 
 ---
 
-> **⚠️ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.
+> **⛔ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.
 
 ---
 

tests/azure-deploy/__snapshots__/triggers.test.ts.snap

@@ -2,23 +2,35 @@
 
 exports[`azure-deploy - Trigger Tests Trigger Keywords Snapshot skill description triggers match snapshot 1`] = `
 {
-  "description": "Deploy validated applications to Azure via azd, Bicep, or Terraform execution steps. WHEN: "run azd up", "run azd deploy", "deploy to Azure", "bicep deploy", "terraform apply", "publish to Azure", "go live".",
+  "description": "Deploy already-prepared applications to Azure by running azd up, azd deploy, or infrastructure provisioning commands. Supports Bicep and Terraform projects. WHEN: "run azd up", "run azd deploy", "execute deployment", "provision infrastructure", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure".",
   "extractedKeywords": [
+    "already-prepared",
     "applications",
     "apply",
     "azure",
     "bicep",
     "cli",
+    "cloud",
+    "commands",
     "deploy",
-    "execution",
+    "deployment",
+    "execute",
+    "function",
     "identity",
+    "infrastructure",
+    "launch",
     "live",
     "mcp",
+    "production",
+    "projects",
+    "provision",
+    "provisioning",
     "publish",
-    "sql",
-    "steps",
+    "push",
+    "running",
+    "ship",
+    "supports",
     "terraform",
-    "validated",
     "validation",
     "when",
   ],
@@ -28,21 +40,33 @@ exports[`azure-deploy - Trigger Tests Trigger Keywords Snapshot skill descriptio
 
 exports[`azure-deploy - Trigger Tests Trigger Keywords Snapshot skill keywords match snapshot 1`] = `
 [
+  "already-prepared",
   "applications",
   "apply",
   "azure",
   "bicep",
   "cli",
+  "cloud",
+  "commands",
   "deploy",
-  "execution",
+  "deployment",
+  "execute",
+  "function",
   "identity",
+  "infrastructure",
+  "launch",
   "live",
   "mcp",
+  "production",
+  "projects",
+  "provision",
+  "provisioning",
   "publish",
-  "sql",
-  "steps",
+  "push",
+  "running",
+  "ship",
+  "supports",
   "terraform",
-  "validated",
   "validation",
   "when",
 ]

tests/azure-prepare/__snapshots__/triggers.test.ts.snap

@@ -2,82 +2,114 @@
 
 exports[`azure-prepare - Trigger Tests Trigger Keywords Snapshot skill description triggers match snapshot 1`] = `
 {
-  "description": "Prepare applications for Azure deployment, except cross-cloud scenarios (use azure-cloud-migrate). Generates or updates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles. WHEN: "prepare app for Azure", "build web app and host on Azure", "move on-premises application to Azure", "configure Azure hosting", "create Azure app", "add Azure service", "modernize app for Azure", "generate azure.yaml", "generate Bicep", "generate Terraform", "create Azure Functions app".",
+  "description": "Default entry point for Azure application development EXCEPT cross-cloud migration — use azure-cloud-migrate instead. Analyzes your project and prepares it for Azure deployment by generating infrastructure code (Bicep/Terraform), azure.yaml, and Dockerfiles. WHEN: "create an app", "build a web app", "create API", "create frontend", "create backend", "add a feature", "build a service", "develop a project", "modernize my code", "update my application", "add database", "add authentication", "add caching", "deploy to Azure", "host on Azure", "Azure with terraform", "Azure with azd", "generate azure.yaml", "generate Bicep", "generate Terraform", "create Azure Functions app", "create serverless HTTP API", "create function app", "create event-driven function", "create and deploy to Azure", "create Azure Functions and deploy", "create function app and deploy".",
   "extractedKeywords": [
+    "analyzes",
     "application",
-    "applications",
+    "authentication",
     "azure",
     "azure-cloud-migrate",
+    "backend",
     "bicep",
     "build",
+    "caching",
     "cli",
-    "configure",
+    "code",
     "create",
     "cross-cloud",
+    "database",
+    "default",
     "deploy",
     "deployment",
+    "develop",
+    "development",
     "dockerfiles",
+    "entry",
+    "event-driven",
     "except",
+    "feature",
+    "frontend",
     "function",
     "functions",
     "generate",
-    "generates",
+    "generating",
     "host",
-    "hosting",
+    "http",
     "identity",
     "infrastructure",
+    "instead",
+    "migration",
     "modernize",
-    "move",
-    "on-premises",
+    "point",
     "prepare",
-    "scenarios",
+    "prepares",
+    "project",
     "security",
+    "serverless",
     "service",
     "terraform",
-    "updates",
+    "update",
     "validation",
     "when",
+    "with",
     "yaml",
+    "your",
   ],
   "name": "azure-prepare",
 }
 `;
 
 exports[`azure-prepare - Trigger Tests Trigger Keywords Snapshot skill keywords match snapshot 1`] = `
 [
+  "analyzes",
   "application",
-  "applications",
+  "authentication",
   "azure",
   "azure-cloud-migrate",
+  "backend",
   "bicep",
   "build",
+  "caching",
   "cli",
-  "configure",
+  "code",
   "create",
   "cross-cloud",
+  "database",
+  "default",
   "deploy",
   "deployment",
+  "develop",
+  "development",
   "dockerfiles",
+  "entry",
+  "event-driven",
   "except",
+  "feature",
+  "frontend",
   "function",
   "functions",
   "generate",
-  "generates",
+  "generating",
   "host",
-  "hosting",
+  "http",
   "identity",
   "infrastructure",
+  "instead",
+  "migration",
   "modernize",
-  "move",
-  "on-premises",
+  "point",
   "prepare",
-  "scenarios",
+  "prepares",
+  "project",
   "security",
+  "serverless",
   "service",
   "terraform",
-  "updates",
+  "update",
   "validation",
   "when",
+  "with",
   "yaml",
+  "your",
 ]
 `;