skilld
All skills
microsoft avatar

/azure-app-onboard-prereq

@ae5e585
by microsoftmicrosoft/skills3.1k stars
351

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/microsoft/skills/azure-app-onboard-prereq

This session only. Nothing lands on disk.

referencesprereq-artifacts.md

≈601 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.

Source: SKILL.md on GitHub

Third-party checks

1 warning1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill is an Azure deployment readiness evaluator authored by Microsoft. It performs static analysis of repositories to identify deployment blockers and can offer to fix them or generate starter code. While the skill has capabilities to execute build commands and modify files, these actions are strictly protected by user consent gates and are limited to the skill's intended purpose of onboarding applications to Azure.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at ae5e585. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month

Capability

metadata
{
  "author": "Microsoft",
  "version": "1.2.2"
}

README badge

README badge for microsoft/skills/azure-app-onboard-prereq