Add --no-prompt to azd env new commands to prevent interactive blocking

.azure/deployment-plan.md

@@ -0,0 +1,190 @@
+# Azure Deployment Plan
+
+> **Status:** Planning
+
+Generated: 2026-04-14
+
+---
+
+## 1. Project Overview
+
+**Goal:** Create and deploy a new production Node.js/TypeScript web application on Azure VMSS with Azure SQL backend, autoscaling, and Application Gateway load balancing.
+
+**Path:** New Project
+
+---
+
+## 2. Requirements
+
+| Attribute | Value |
+|-----------|-------|
+| Classification | Production |
+| Scale | Large (high traffic, autoscaling) |
+| Budget | Balanced |
+| **Subscription** | Playground - 01 (`4b0a7581-9eea-4d30-a166-f8fac23b6edd`) |
+| **Location** | East US |
+| OS | Linux (Ubuntu) |
+| VM Size | Standard_D4s_v5 (4 vCPUs, 16 GB RAM) |
+| Hosting Model | VMSS (Flexible orchestration) |
+
+---
+
+## 3. Components Detected
+
+| Component | Type | Technology | Path |
+|-----------|------|------------|------|
+| Web App | SSR Web Server | Node.js / TypeScript / Express | `src/web/` |
+| Database | Relational DB | Azure SQL | (managed service) |
+
+---
+
+## 4. Recipe Selection
+
+**Selected:** Bicep
+
+**Rationale:** User preference for native Azure IaC. Bicep provides first-class ARM integration, strong typing, and is ideal for VMSS + networking + SQL deployments.
+
+---
+
+## 5. Architecture
+
+**Stack:** VMSS (Virtual Machine Scale Set) + Azure SQL
+
+### Service Mapping
+
+| Component | Azure Service | SKU / Config |
+|-----------|---------------|--------------|
+| Web App (VMSS) | Microsoft.Compute/virtualMachineScaleSets | Standard_D4s_v5, Flexible orchestration, 2–6 instances |
+| Load Balancer | Microsoft.Network/applicationGateways | Application Gateway v2 (L7, TLS offload) |
+| Database | Microsoft.Sql/servers + databases | Azure SQL S2 (50 DTU) |
+| Virtual Network | Microsoft.Network/virtualNetworks | /16 VNet with subnets for VMSS, AppGW, SQL |
+| NSG | Microsoft.Network/networkSecurityGroups | Allow HTTP/HTTPS inbound, restrict SSH |
+| Public IP | Microsoft.Network/publicIPAddresses | Standard SKU, static, for AppGW frontend |
+
+### Supporting Services
+
+| Service | Purpose |
+|---------|---------|
+| Log Analytics | Centralized logging |
+| Application Insights | Monitoring & APM |
+| Key Vault | Secrets management (DB connection string) |
+| Managed Identity | VMSS-to-SQL and VMSS-to-KeyVault auth |
+
+### Autoscale Configuration
+
+| Setting | Value |
+|---------|-------|
+| Metric | CPU percentage |
+| Scale-out threshold | 70% avg CPU for 5 min |
+| Scale-in threshold | 30% avg CPU for 10 min |
+| Min instances | 2 |
+| Max instances | 6 |
+| Cooldown | 5 minutes |
+
+### Network Architecture
+
+```
+Internet → Public IP → Application Gateway (L7/TLS) → VMSS Subnet → VM instances
+                                                                    ↓
+                                                              SQL Private Endpoint
+```
+
+---
+
+## 6. Provisioning Limit Checklist
+
+### Resource Inventory & Quota Validation
+
+| Resource Type | Number to Deploy | Total After Deployment | Limit/Quota | Notes |
+|---------------|------------------|------------------------|-------------|-------|
+| Microsoft.Compute vCPUs (standardDSv5Family) | 24 (6×4 max) | 24 | 350 | ✅ Fetched from: az vm list-usage |
+| Microsoft.Compute vCPUs (Total Regional) | 24 | 180 | 350 | ✅ Fetched from: az vm list-usage |
+| Microsoft.Compute/virtualMachines | 6 (max) | 47 | 25,000 | ✅ Fetched from: az vm list-usage |
+| Microsoft.Network/virtualNetworks | 1 | 62 | 1,000 | ✅ Fetched from: az network list-usages |
+| Microsoft.Network/publicIPAddresses | 1 | 70 | 1,000 | ✅ Fetched from: az network list-usages |
+| Microsoft.Network/networkSecurityGroups | 2 | 216 | 5,000 | ✅ Fetched from: az network list-usages |
+| Microsoft.Network/loadBalancers (Standard) | 1 (AppGW) | 49 | 1,000 | ✅ Fetched from: az network list-usages |
+| Microsoft.Sql/servers | 1 | 2 | 20 per region | ✅ Fetched from: Azure Resource Graph + official docs |
+| Microsoft.KeyVault/vaults | 1 | ~1 | 10,000 per region | ✅ Fetched from: official docs |
+| Microsoft.OperationalInsights/workspaces | 1 | ~1 | 50 per region | ✅ Fetched from: official docs |
+
+**Status:** ✅ All resources within limits
+
+---
+
+## 7. Execution Checklist
+
+### Phase 1: Planning
+- [x] Analyze workspace (new project)
+- [x] Gather requirements (production, large, balanced, Linux)
+- [x] Confirm subscription and location with user (Playground - 01, eastus)
+- [x] Prepare resource inventory
+- [x] Fetch quotas and validate capacity
+- [x] Scan codebase (N/A — new project)
+- [x] Select recipe (Bicep)
+- [x] Plan architecture (VMSS + AppGW + SQL)
+- [ ] **User approved this plan**
+
+### Phase 2: Execution
+- [ ] Research components (load Bicep references)
+- [ ] Generate infrastructure files (`infra/main.bicep`, modules)
+- [ ] Generate application code (`src/web/` — Express/TypeScript app)
+- [ ] Generate custom-data script (cloud-init to bootstrap Node.js on VMs)
+- [ ] Generate application configuration
+- [ ] Apply security hardening (NSG rules, Key Vault, managed identity)
+- [ ] ⛔ Update plan status to "Ready for Validation"
+
+### Phase 3: Validation
+- [ ] Invoke azure-validate skill
+- [ ] All validation checks pass
+- [ ] Update plan status to "Validated"
+
+### Phase 4: Deployment
+- [ ] Invoke azure-deploy skill
+- [ ] Deployment successful
+- [ ] Report deployed endpoint URLs
+- [ ] Update plan status to "Deployed"
+
+---
+
+## 8. Files to Generate
+
+| File | Purpose | Status |
+|------|---------|--------|
+| `.azure/deployment-plan.md` | This plan | ✅ |
+| `infra/main.bicep` | Root Bicep template | ⏳ |
+| `infra/modules/vmss.bicep` | VMSS + autoscale config | ⏳ |
+| `infra/modules/network.bicep` | VNet, subnets, NSG, AppGW | ⏳ |
+| `infra/modules/sql.bicep` | Azure SQL Server + Database | ⏳ |
+| `infra/modules/monitoring.bicep` | Log Analytics + App Insights | ⏳ |
+| `infra/modules/keyvault.bicep` | Key Vault + secrets | ⏳ |
+| `infra/cloud-init.yaml` | VM bootstrap script (Node.js setup) | ⏳ |
+| `src/web/package.json` | Node.js dependencies | ⏳ |
+| `src/web/tsconfig.json` | TypeScript config | ⏳ |
+| `src/web/src/index.ts` | Express app entry point | ⏳ |
+
+---
+
+## 9. Cost Estimate
+
+| Resource | Unit Cost | Monthly Estimate |
+|----------|-----------|-----------------|
+| VMSS (2–6× Standard_D4s_v5) | $0.192/hr per VM | $280–$840 |
+| Application Gateway v2 | ~$0.246/hr + data | ~$180 |
+| Azure SQL S2 (50 DTU) | ~$75/mo | ~$75 |
+| Log Analytics (5 GB/day) | ~$2.30/GB | ~$350 |
+| Key Vault | ~$0.03/10K ops | <$5 |
+| **Total estimate** | | **~$885–$1,450/mo** |
+
+> 💡 Consider 1-year reserved instances for VMSS to save ~35%.
+
+---
+
+## 10. Next Steps
+
+> Current: Awaiting user approval
+
+1. User approves this plan
+2. Generate all infrastructure and application files
+3. Validate with azure-validate
+4. Deploy with azure-deploy

.gitattributes

@@ -0,0 +1,2 @@
+.github/workflows/*.lock.yml linguist-generated=true merge=ours
+*.sh text eol=lf

.github/CODEOWNERS

@@ -0,0 +1,34 @@
+# This is a CODEOWNERS file for the GitHub-Copilot-for-Azure repository.
+# Each line is a file pattern followed by one or more code owners.
+
+# Default owners for everything in the repo
+* @microsoft/ghcp4a
+
+# Workflow files — explicit protection (changes require team review)
+/.github/workflows/ @microsoft/ghcp4a
+
+# Plugin skills owners
+/plugin/skills/appinsights-instrumentation/ @JasonYeMSFT
+/plugin/skills/azure-ai/ @charris-msft
+/plugin/skills/azure-aigateway/ @azaslonov
+/plugin/skills/azure-cloud-migrate/ @saikoumudi @MadhuraBharadwaj-MSFT
+/plugin/skills/azure-compliance/ @saikoumudi
+/plugin/skills/azure-compute/ @alex-thompson @rakal-dyh @joybb @rmmue21
+/plugin/skills/azure-cost-optimization/ @saikoumudi
+/plugin/skills/azure-deploy/ @tmeschter @wbreza @kvenkatrajan @paulyuk
+/plugin/skills/azure-diagnostics/ @tmeschter @saikoumudi
+/plugin/skills/azure-enterprise-infra-planner/ @Jbrocket @micha31r @arunrab
+/plugin/skills/azure-hosted-copilot-sdk/ @jongio
+/plugin/skills/azure-kubernetes/ @saikoumudi @chandraneel
+/plugin/skills/azure-kusto/ @saikoumudi
+/plugin/skills/azure-messaging/ @kashifkhan
+/plugin/skills/azure-prepare/ @tmeschter @wbreza @kvenkatrajan
+/plugin/skills/azure-quotas/ @rakal-dyh
+/plugin/skills/azure-rbac/ @JasonYeMSFT @msalaman
+/plugin/skills/azure-resource-lookup/ @charris-msft
+/plugin/skills/azure-resource-visualizer/ @tmeschter
+/plugin/skills/azure-storage/ @charris-msft
+/plugin/skills/azure-upgrade/ @MadhuraBharadwaj-MSFT @saikoumudi
+/plugin/skills/azure-validate/ @wbreza @tmeschter @kvenkatrajan
+/plugin/skills/entra-app-registration/ @JasonYeMSFT @kvenkatrajan
+/plugin/skills/microsoft-foundry/ @ankitbko @tendau @XOEEst

.github/ISSUE_TEMPLATE/skill_bug_report.yml

@@ -0,0 +1,97 @@
+name: Report a Skill Bug
+title: "[Skill Bug]: "
+description: Report a bug related to Azure skills in GitHub Copilot for Azure
+type: "Bug"
+labels:
+  - "bug"
+  - "skills"
+body:
+  - type: checkboxes
+    id: pre-flight
+    attributes:
+      label: Preflight Checklist
+      description: "Before submitting an issue, please make sure you've done the following:"
+      options:
+        - label: I have installed the [latest version of GitHub Copilot for Azure in VS Code](https://github.com/microsoft/GitHub-Copilot-for-Azure/releases/latest).
+          required: true
+        - label: I have checked existing resources, including using the /help command in the chat window.
+          required: true
+        - label: I have searched for [similar issues](https://github.com/microsoft/GitHub-Copilot-for-Azure/issues).
+          required: true
+
+  - type: markdown
+    attributes:
+      value: ---
+
+  - type: textarea
+    id: repro-steps
+    attributes:
+      label: Repro Steps
+      description: Provide numbered steps to reproduce the issue
+      placeholder: |
+        1. Open VS Code with GitHub Copilot for Azure
+        2. Use the prompt "..."
+        3. Observe the error
+    validations:
+      required: true
+
+  - type: textarea
+    id: prompt
+    attributes:
+      label: Prompt
+      description: Provide the exact text/prompt used when encountering the issue
+      placeholder: Copy and paste the exact prompt you used
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: ---
+
+  - type: textarea
+    id: expected-result
+    attributes:
+      label: Expected Result
+      description: What did you expect to happen?
+      placeholder: Describe what you expected to occur
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual-result
+    attributes:
+      label: Actual Result
+      description: What actually happened?
+      placeholder: Describe what actually occurred
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: ---
+
+  - type: textarea
+    id: attachments
+    attributes:
+      label: Attachments
+      description: Attach logs, error messages, screenshots, or any other relevant files
+      placeholder: |
+        Drag and drop files here, or paste screenshots
+        Include error messages, logs, or any other relevant information
+
+  - type: input
+    id: regression
+    attributes:
+      label: Regression?
+      description: Did this work before? If yes, which version did it work in?
+      placeholder: e.g., "Yes, worked in version 1.0.0" or "No, never worked"
+
+  - type: markdown
+    attributes:
+      value: ---
+
+  - type: input
+    id: context
+    attributes:
+      label: Additional Context
+      description: Add any other details, such as Azure subscription type, network restrictions, etc.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+## Description
+
+<!-- Briefly describe what this PR changes and why. -->
+
+## Checklist
+
+- [ ] Tests pass locally (`cd tests && npm test`)
+- [ ] **If modifying skill descriptions:** verified routing correctness with integration tests (`npm run test:skills:integration -- <skill>`)
+- [ ] **If modifying skill `USE FOR` / `DO NOT USE FOR` / `PREFER OVER` clauses:** confirmed no routing regressions for competing skills
+- [ ] Version bumped in skill frontmatter (if skill files changed)
+
+## Related Issues
+
+<!-- Link to related issues, e.g. Fixes #1234 -->

.github/agents/SkillBrainstormer.agent.md

@@ -0,0 +1,46 @@
+---
+name: Azure Skill Brainstormer
+description: Helps brainstorm ideas for a new Azure-related agent skill based on user provided tools and documentation.
+tools: ['execute', 'read', 'search', 'web', 'agent', 'azure-mcp/*', 'todo']
+handoffs:
+  - label: Gather further requirements
+    agent: Azure Skill Creator
+    prompt: Gather any further requirements for the described skill
+    send: true
+---
+
+# Skill Brainstormer Agent
+
+This agent assists users in brainstorming ideas for new agent skills by leveraging provided tools and documentation. It guides users through a structured brainstorming process to generate innovative and feasible skill concepts.
+
+# Responsibilities
+
+## Gathering Inputs
+
+Ask the user for the following information:
+- A list of MCP tools they would like to utilize.
+- Any specific command line tools they would like to utilize.
+- Links to any relevant documentation or resources.
+- Any specific scenarios or problems they want the skill to address.
+
+Ask for these requirements one at a time so that you don't overwhelm the user with questions. Summarize their responses before moving on. Make sure to clarify any ambiguous points with follow-up questions.
+
+## Researching Information
+
+General information on agent skills can be found at [Agent Skills](https://agentskills.io/). This includes an overview of what agent skills are, how they function, best practices for their development, and detailed specifications.
+
+Based on the user's requirements, research and gather any additional background information that may be relevant to the skill. This may include:
+- Existing Azure services or APIs that the skill will interact with.
+- Relevant MCP tools and their capabilities (especially Azure MCP).
+- Relevant command line tools and their capabilities.
+
+Run any specified command line tools with the -h, -?, or --help flags to gather information about their usage and options.
+
+Review the descriptions and inputs of the specified MCP tools.
+
+# Output
+
+Once you have the requirements and have completed the research, help the user brainstorm potential skill ideas. Create the following:
+- a list of up to five scenarios where the skill could be useful
+- examples of using the underlying command line tools, MCP tools, and information from the documentation to address those scenarios
+- a brief description of the skill idea, including its purpose and key features