azure-app-onboard-prereq
Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".
- License 许可
- MIT
- 所属仓库
- microsoft/skills
- 最近更新
- 2026-11-14
- Stars
- ★ 3.2k
- Forks
- 368
01 前言 Front Matter
- name
- azure-app-onboard-prereq
- license
- MIT
- metadata
- { "author": "Microsoft", "version": "1.2.5" }
- description
- Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".
02 资源文件 15
- 参考文档references/build-check.md5.7 KB
- 参考文档references/cloud-sdk-migration.md2.2 KB
- 参考文档references/completeness-check.md4.4 KB
- 参考文档references/component-mapping.md4.6 KB
- 参考文档references/dependency-compatibility.md10.0 KB
- 参考文档references/deployability-check.md3.1 KB
- 参考文档references/prereq-artifacts.md2.3 KB
- 脚本references/prereq-schemas.ts4.2 KB
- 参考文档references/readiness-gate.md5.4 KB
- 参考文档references/remediation-protocol.md3.6 KB
- 参考文档references/session-protocol.md7.4 KB
- 脚本references/session-schemas.ts5.2 KB
- 参考文档references/subagent-starter-scaffold.md4.0 KB
- 参考文档references/subscription-resolution.md1.8 KB
- 参考文档references/zero-code-path.md3.6 KB
03 SKILL.md 正文
Azure App Onboard Prereq — Repository Evaluation
Evaluate a user's repository for build health, app completeness, and Azure deployment feasibility — before infrastructure planning. Produces per-component verdicts (PASS/WARN/FAIL) consumed by downstream phases.
Orchestrator relationship: Called by
azure-app-onboardat Step 3, or standalone for code readiness checks. When called by orchestrator, return control toazure-app-onboardafter writing artifacts — do NOT invoke downstream phases directly.
Phase 1 of 4 in AppOnboard pipeline. Session: .copilot-azure/sessions/{session-id}/. Reads context.json. Writes components[], repo{}, detectedInfra[]. Produces prereq-output.json. Schema: prereq-schemas.ts — PrereqOutput, BuildRequirements. Direct entry supported.
When NOT to Use
| Signal | Redirect |
|---|---|
| Validate infrastructure (Bicep/TF/azure.yaml) | azure-validate |
| Generate IaC | azure-prepare |
| End-to-end idea-to-production | azure-app-onboard |
Run azd up or deploy |
azure-deploy |
Rules
⛔ ABSOLUTE PROHIBITION —
npm install,npm test,npx jest,pytest, and ALL install/build/test commands are NEVER allowed. Under NO circumstances may you runnpm install,npm test,npx jest,pip install,pytest,dotnet build,dotnet restore,dotnet test,go mod download,cargo build, or ANY package-manager install, build, or test command during the prereq phase. Do NOT run test suites to verify code — check for test config files statically instead. The prereq phase is read-only evaluation + static-only verification. ONLY exception — two sanctioned contexts, both consent-gated: (a) code the agent modified during migration/remediation (see remediation-protocol.md step 6), or (b) code the agent wrote from scratch on the zero-code path (see zero-code-path.md). In either case, install/build/test runs ONLY via the user-confirmed build-validation gate (build-check.md Step 3), after the user answers that specific per-command consent prompt. General prior consent never counts.
- ⛔ Full pipeline (Steps 1–8), no exceptions. All prompts → Step 1 directly. Answer specific questions AS PART OF findings (Step 5), not before.
- ⛔ No sub-agents for evaluation. 3-axis evaluation is inline. Exception: zero-code-path scaffolding (Step 2).
- Code/destructive modifications require
ask_user. Max 3 questions before results. Direct entry: don't repeat orchestrator's intent questions.
MCP Tools
| Tool | Purpose |
|---|---|
mcp_azure_mcp_get_azure_bestpractices |
Validate detected stack patterns against Azure best practices |
mcp_azure_mcp_extension_cli_install |
Check/install required CLI tools (az, azd, func) |
Workflow
Step 1: Session Check
Orchestrator entry: Session exists — read context.json, proceed to Step 2.
Direct entry: Check .copilot-azure/sessions/active-session.json:
- Exists → ⛔ read session-protocol.md for resume/fresh gate. Do NOT proceed until user answers.
- Missing → create session: generate UUID,
New-Item -ItemType Directory -Path ".copilot-azure/sessions/{uuid}" -Force, writecontext.json+active-session.jsonviacreatetool.
Then: az account show → merge {id, name, tenantId} into context.json.azure. ⛔ Session MUST exist on disk before any scanning.
Step 2: Scan Workspace
Scan for project files. Detect components, repo{}, detectedInfra[], detectedServices[]. Classify Terraform providers. Check CLI availability. Stack detection conflicts: user explicit statement wins (write to context.json, mark scan as override); scan-only → confirm with user; multiple stacks → show all and ask (see component-mapping.md); no code → zero-code-path.md.
If no project files, no Dockerfile, AND no index.html → ⛔ read zero-code-path.md.
⛔ Cloud SDK early gate. Grep for
aws-sdk|@aws-sdk|boto3|google-cloud|@google-cloud|firebase. If functional deps found → read cloud-sdk-migration.md, thenask_user: "Redirect to Azure Cloud Migrate" (setrouteToSkill: "azure-cloud-migrate") · "Continue evaluation anyway" (finish readiness eval + SDK→Azure mapping, then STOP at Step 8 — no plan until the deps are swapped) · "Cancel".
Step 3: Per-Component Evaluation
| Sub-step | Action | Reference |
|---|---|---|
| 3.1 | Build check | ⛔ You MUST read build-check.md |
| 3.2 | Completeness check | ⛔ You MUST read completeness-check.md |
| 3.3 | Deployability check | ⛔ You MUST read deployability-check.md |
| 3.3a | Component mapping (conditional) | Read component-mapping.md ONLY IF >1 project manifest found (monorepo) |
Populate buildRequirements per component after evaluation. Verdict propagation, tier rules, and f1Viable aggregation are in readiness-gate.md and the individual check references.
Step 4: Write Artifacts + Readiness Gate
⛔ Verify context.json exists on disk. ⛔ You MUST read readiness-gate.md (verdicts, tiers, batch-then-approve, fast-track), then ⛔ You MUST read prereq-artifacts.md (write procedures, schemas).
Step 5: Present Findings
Per readiness-gate.md § Present Findings — show verdicts grouped by severity before proceeding.
Step 6: Remediation (conditional)
⛔ You MUST read remediation-protocol.md IF any ❌ FAIL verdict, ? Recommended Fix, or ⚠️ WARN with fixPhase: "prereq" exists. Contains remediation loop, static verification, re-eval mandate, post-remediation artifact updates, and the build-validation consent gate. If all verdicts are ✅ PASS or ⚠️ WARN without fixPhase: "prereq", skip to Step 7.
Step 7: Write Final State
completedPhases already has "prereq" + currentPhase: null (from Step 4). Then:
⛔ Write
lastScanCommit. Rungit rev-parse HEADand store the full 40-character SHA ascontext.json.repo.lastScanCommit. Required — staleness guard in Step 1 compares to HEAD on resume to detect changes.
Step 8: Route
⛔ Mandatory — do NOT skip this step.
Routing fields: All routing writes
routeToSkillandrouteReasontocontext.json.
Post-remediation context: If Step 6 ran, lead the routing prompt with: "Remediation complete — {N} issues fixed, your app is now {overallHealth}."
⛔ Evaluate rows top to bottom — first match wins.
| # | Condition | Action |
|---|---|---|
| 1 | routeToSkill set (any entry) |
ask_user: "Redirect to {routeToSkill}" / "Not now". ⛔ Pipeline stops — do NOT proceed to architecture planning. |
| 2 | cloudSdkFindings[] non-empty (user chose "Continue evaluation anyway") |
Present the cloud-SDK → Azure swap mapping as ? blockers, then ask_user with this exact prompt: "? Cloud SDK migration required — these dependencies must be swapped before this app can deploy to Azure. (Redirect to azure-cloud-migrate / Stop — swap manually and re-run)" — Redirect sets routeToSkill: "azure-cloud-migrate", Stop halts. ⛔ Pipeline stops — do NOT proceed to architecture planning, and do NOT offer a "continue to prepare" option; the app can't deploy until the deps are swapped. |
| 3 | Orchestrator + no routeToSkill |
Tell the user: "✅ Your app has been evaluated and is ready — let's plan your Azure deployment." Then invoke azure-app-onboard. ⛔ Do NOT stop, do NOT wait for user input, do NOT narrate internal handoffs. The user already consented to the full pipeline at scope triage. |
| 4 | Direct + ready/readyWithCaveats + no Azure infra | ask_user: "Deploy to Azure (full pipeline)" → invoke azure-app-onboard / "Not now" |
| 5 | Direct + ready/readyWithCaveats + existing Azure infra | ask_user: "Start fresh" → invoke azure-app-onboard / "Use existing infra" → invoke azure-prepare / "Not now" |
| 6 | Direct + blocked | Report blocker summary + "Fix and re-run." |
Severity tiers (??❌?⚠️✅) are defined in readiness-gate.md.
Outputs
| Artifact | Location | Consumer |
|---|---|---|
| Session context | context.json → components[], repo{}, detectedInfra[], detectedServices[] |
All downstream phases |
| Prereq output | prereq-output.json |
prepare phase (via azure-app-onboard) |
| Readiness report | .copilot-azure/sessions/{uuid}/readiness-report.md |
User (offline reference) |
04 同仓库更多 Skills
azure-advisor-cost-optimization
Analyze Azure Advisor Cost/IdleResources findings and prevalidate deletion safety, including Service Groups. WHEN: "find unused Azure resources", "what resources am I paying for but no longer using", "idle-resource savings", "historical idle-resource savings", "are these idle resources safe to delete". Generic Cost, other subcategories, and cross-category requests use azure-advisor.
skill-creator
Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
podcast-generation
Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.
microsoft-docs
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).
kql
KQL language expertise for writing correct, efficient Kusto Query Language queries. Covers syntax gotchas, join patterns, dynamic types, datetime pitfalls, regex patterns, serialization, memory management, result-size discipline, and advanced functions (geo, vector, graph). USE THIS SKILL whenever writing, debugging, or reviewing KQL queries — even simple ones — because the gotchas section prevents the most common errors that waste tool calls and cause expensive retry cascades. Trigger on: KQL, Kusto, ADX, Azure Data Explorer, Fabric Real-Time Intelligence, EventHouse, Log Analytics, log analysis, data exploration, time series, anomaly detection, summarize, where clause, join, extend, project, let statement, parse operator, extract function, any mention of pipe-forward query syntax.