AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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".

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-app-onboard-prereq at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 14

references/prereq-artifacts.md

Artifact write procedures for the prereq phase exit. Read at Step 4 of the readiness gate.

Write Artifacts

⛔ Write all 3 artifacts before exiting prereq. Downstream phases read these. ⛔ Use create tool for ALL session files — NEVER powershell. Terminal is OK ONLY for read-only ops: UUID generation, git info, file existence checks. ⛔ Path scoping: ALL create calls target .copilot-azure/sessions/{uuid}/. After writing, read back to confirm correct path.

  1. prereq-output.json — ⛔ Read prereq-schemas.ts for PrereqOutput interface.

    ⛔ Per-component verdicts MUST persist. Every entry in components[] MUST include a verdicts object: { "build", "completeness", "deployability" } with values PASS/WARN/FAIL (build may be SKIPPED when build validation was skipped; completeness/deployability are never SKIPPED). Downstream readiness scoring and the prepare phase read these — never omit them.

    ⛔ Warnings MUST persist. Every ⚠️ WARN → warnings[]: { "id": "W-{ID}", "component", "axis", "summary", "detail", "fix", "fixPhase" }. Both fix and fixPhase are required — validate before writing.

    ⛔ Health endpoint: Write detected path to healthEndpoint (e.g., "/api/v1/health/"). If none → null + W-HEALTH warning with fixPhase: "scaffold".

    ⛔ Entry point: Write to entryPoint (e.g., "index.js"). null for .NET/Go/Java (Oryx handles startup).

    ⛔ postDeployRecommendations[]: For each ⚠️ WARN, write per PostDeployRecommendation schema from session-schemas.ts: { "title", "reason", "effort": "low|medium|high", "services": [] }.

  2. context.json — ⛔ Use edit (not create — Step 1 already created it). Populate components[], repo, detectedInfra[], detectedServices[], app.name (from primary component's project manifest or workspace root dir name). Append "prereq" to completedPhases NOW (before presenting), set currentPhase: null, update lastModifiedUtc.

  3. readiness-report.md — Summary table (Build/Completeness/Deployability verdicts), detected stack, all warnings with actionable detail. Clean markdown, no rigid template.

⛔ Phase exit gate: All 3 artifacts must exist. If any missing, write NOW.